-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 11.3.11
-
Component/s: Data Center - Index
-
None
-
11.03
-
1
-
Severity 3 - Minor
Issue Summary
Post upgrade to 11.3.11, restarting of Jira is delayed with indexqueue congestion and the 30-second timeout messages on RMI threads for DBR/cache replication
Steps to Reproduce
- Upgrade instance to 11.3.11
- Restart Jira node
Expected Results
Jira should start gracefully without such RMI timeout exceptions.
Actual Results
The below exception is thrown in the xxxxxxx.log file:
2026-09-07 18:40:19,595+0000 RMI TCP Connection(32)-172.30.83.12 ERROR [c.a.j.issue.index.IndexLock] Wait attempt timed out - waited 30000 milliseconds com.atlassian.jira.issue.index.IndexException: Wait attempt timed out - waited 30000 milliseconds
Workaround
This is harmless and would only cause the delay in startup, It could be avoided by adding below mentioned dark feature enabled:
com.atlassian.jira.plugin.event.field.refresh.enabled
The flag does not change RMI or index locking. It reduces the schema-refresh workload by ignoring generic SearchHandlerRefreshedEvent events and refreshing only for relevant plugin modules and explicit custom-field changes.
- is related to
-
JRASERVER-79506 Deadlock detected in Jira startup when concurrent cache invalidation and index schema rebuild acquire shared locks.
-
- Closed
-