-
Bug
-
Resolution: Fixed
-
Major
-
None
-
-
Jenkns Core 2.163
Jenkins does not start due to a deadlockJenkins does not start due to a deadlock
The issue we are facing is very similar to JENKINS-49038.We have upgraded Jenkins instance from 2.121 to 2.138.2.2.The instance service starts normally, but the UI is loading infinitely long.At startup we get the deadlock
// output "PreventRefreshFilter.initAutoRefreshFilter" #57 daemon prio=5 os_prio=0 tid=0x00007fdb5c02f800 nid=0x58ad waiting for monitor entry [0x00007fdb20193000] java.lang.Thread.State: BLOCKED (on object monitor) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) - waiting to lock <0x00000006c0120260> (a hudson.ExtensionList$Lock) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:192) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:318) - locked <0x00000006c37c7680> (a hudson.DescriptorExtensionList) at hudson.ExtensionList.iterator(ExtensionList.java:172) at hudson.ExtensionList.get(ExtensionList.java:149) at hudson.plugins.claim.ClaimConfig.get(ClaimConfig.java:202) at hudson.plugins.claim.http.PreventRefreshFilter.initAutoRefreshFilter(PreventRefreshFilter.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1069) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
The deadlock seems to be intermittent, i.e. when stopping and starting the instance, it may finally start 2 times of 10.The issue can not be reproduced on a clean instance without custom plugins (only default plugins installed).
- is related to
-
JENKINS-49038 Jenkins does not start due to a deadlock
- Resolved
-
JENKINS-55361 DescriptorExtensionList not locking correctly, leading to deadlocks
- Resolved