-
Bug
-
Resolution: Fixed
-
High
-
10.124.3
-
None
-
2
-
Severity 2 - Major
-
No
Issue Summary
Some customers have reported intermittent performance degradation in their JA instances across different pages and most notably in roadmaps.
Steps to Reproduce
- No specific steps but the page would feel sluggish
Expected Results
–
Actual Results
The below exception is thrown in the Splunk logs
Exception: System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 176) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Workaround
A DB restart would temporarily clear the locks but eventually will build up again.
- is resolved by
-
HOT-105470 Loading...
- mentioned in
-
Page Loading...