Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
None
-
None
-
4
-
Severity 2 - Major
-
Description
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
The existing workarounds we have for the problem with 'Issue ranking operation log entry found where none expected' described in this JIRA Agile knowledge-base article: https://confluence.atlassian.com/pages/viewpage.action?pageId=269982614 would always require a JIRA restart.
- For now it doesn't appear we know the root cause of this problem, this could be looked into and possibly a prevention of the issue at the source level can be implemented.
- Also, if there is no way to guarantee this problem problem wont occur at the database level, perhaps a solution such that JIRA/JIRA agile is able to automatically remedy this situation when it occurs by clearing out the AO_60DB71_ISSUERANKINGLOG table, without requiring the user to manually restart can be implemented.
Attachments
Issue Links
- is duplicated by
-
JSWSERVER-10541 As an admin I want JIRA Agile to recover more gracefully from database transaction errors
- Closed
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-