My problem doesn't seem to be the same as JENKINS-22558: Found one Java-level deadlock: ============================= "Handling GET /gsm_ci_stage2/threadDump from 150.132.253.50 : RequestHandlerThread[#25] Jenkins/threadDump.jelly Jenkins/sidepanel.jelly View/sidepanel.jelly": waiting to lock monitor 0x00007faa64638ef8 (object 0x00000000c1e0e998, a hudson.model.Queue), which is held by "jenkins.util.Timer [#3]" "jenkins.util.Timer [#3]": waiting to lock monitor 0x00007faa542a2838 (object 0x00000000c2ef23d8, a hudson.slaves.RetentionStrategy$Demand), which is held by "jenkins.util.Timer [#8]" "jenkins.util.Timer [#8]": waiting to lock monitor 0x00007faa64638ef8 (object 0x00000000c1e0e998, a hudson.model.Queue), which is held by "jenkins.util.Timer [#3]"
I agree it would be better to not use jruby for this, but I wanted something that could be distributed alongside a vanilla jenkins war file.Jruby seemed like the best/easiest solution for this. On Wednesday, December 10, 2014 8:14:33 PM UTC+1, Jesse Glick wrote: > > On Wed, Dec 10, 2014 at 11:07 AM, Stephen Connolly > <[email protected] <javascript:>> wrote: > > lots of deadlocks when fighting to make the vmware cloud work > > If I understand correctly, those were analogous to JENKINS-22558. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/735e593f-f97f-4605-86df-f5645359d96c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
