[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2

2018-12-03 Thread kgos...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Gostaf commented on  JENKINS-54974  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2   
 

  
 
 
 
 

 
 Hi Oleg, As per your comment, I've attached report_threads1.log In addition, removing the claim plugin does not solve the issue. Startup then complained about the Radiator view plugin dependency on claim. Disabling the Radiator view plugin does not help. There was still a deadlock after having claim removed and radiatorviewplugin disabled.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2

2018-12-03 Thread kgos...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Gostaf updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54974  
 
 
  Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2   
 

  
 
 
 
 

 
Change By: 
 Kirill Gostaf  
 
 
Attachment: 
 report_threads1.log  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2

2018-12-02 Thread kgos...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Gostaf updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54974  
 
 
  Jenkins does not start due to a deadlock after upgrade from 2.121.2.2 to 2.138.2.2   
 

  
 
 
 
 

 
Change By: 
 Kirill Gostaf  
 
 
Summary: 
 Jenkins does not start due to a deadlock  after upgrade from 2.121.2.2 to 2.138.2.2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54974) Jenkins does not start due to a deadlock

2018-12-02 Thread kgos...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kirill Gostaf created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54974  
 
 
  Jenkins does not start due to a deadlock   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Christian Bremer  
 
 
Components: 
 claim-plugin  
 
 
Created: 
 2018-12-03 07:20  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Kirill Gostaf  
 

  
 
 
 
 

 
 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=0x7fdb5c02f800 nid=0x58ad waiting for monitor entry [0x7fdb20193000]   java.lang.Thread.State: BLOCKED (on object monitor) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) - waiting to lock <0x0006c0120260> (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 <0x0006c37c7680> (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