Details
-
Bug
-
Resolution: Fixed
-
High
-
7.13.0, 8.0.0, 8.8.2, 8.5.11
-
7.13
-
5
-
Severity 2 - Major
-
13
-
Description
Summary
This is a more specific version of JRASERVER-62772 covering scenario when localhost-startStop-1 and localq-reader threads are deadlocking during DC node startup
Any simultaneous calls to <T> T getComponent(final Class<T> componentType) and to <T> List<T> getComponents(final Class<T> componentType) in DefaultPicoContainer from parallel threads can lead to deadlock.
Also it happens on JIRA's startup:
The following error can be found in the logs :
2020-01-08 09:28:37,841 DeadlockDetection:thread-1 ERROR [c.a.jira.startup.LauncherContextListener] A deadlock has been detected on JIRA startup for the following threads: ["localq-reader-0" Id=31 BLOCKED on org.picocontainer.DefaultPicoContainer@1b84f9c1 owned by "localhost-startStop-1" Id=16, "localhost-startStop-1" Id=16 WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@154314c1 owned by "localq-reader-0" Id=31] 2020-01-08 09:28:37,843 DeadlockDetection:thread-1 ERROR [c.a.jira.startup.LauncherContextListener] "localq-reader-0" Id=31 BLOCKED on org.picocontainer.DefaultPicoContainer@1b84f9c1 owned by "localhost-startStop-1" Id=16 2020-01-08 09:28:37,843 DeadlockDetection:thread-1 ERROR [c.a.jira.startup.LauncherContextListener] "localhost-startStop-1" Id=16 WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@154314c1 owned by "localq-reader-0" Id=31
Workaround
- Delete the [JIRA-HOME]/localq/* directory contents
- restart Jira
Attachments
Issue Links
- is cloned from
-
-
- Closed
-
- is related to
-
-
- Gathering Impact
-
- relates to
-
JC-518 Loading...