[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort closed an issue as Fixed Mitch McLaughlin I can guarantee this particular deadlock is resolved. If you're seeing a new deadlock, please open a ticket and include the thread dump in it. Thanks Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: Reopened Closed Resolution: Fixed 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Mitch McLaughlin reopened an issue I just encountered this issue again with a client using workflow-cps:2.53. Let me know what information I can supply to help look into this. Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Mitch McLaughlin Resolution: Done Status: Closed Reopened 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Thomas Becker commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads 2.53 is working fine until now. Thx for the fix! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Lars Bilke commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Sam Van Oort 2.53 is running for me without a deadlock too so far... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Reinhold Füreder commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Sam Van Oort Thanks for the hint (that is of course fully correct, as I have just seen: "There is an update available for 'workflow-cps:2.51' plugin: 2.53") => I'll try that... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Reinhold Füreder Please try the 2.53 update released today – you appear to have the original deadlock noted between the TimingFlowNodeStorage and things synchronizing on the execution that was fixed in 2.52 and the 2.53 includes an additional fix for the other deadlock noted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Reinhold Füreder commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads JFYI: We experienced the same "Deadlock in CpsFlowExecution" problem yesterday (once), cf. also JENKINS-51123 And we also see the block in thread "WorkflowRun.copyLogs", besides several threads "Handling GET /job/ACME-Pipeline/wfapi/runs from 10.x.x.x : RequestHandlerThreadx" and "Handling GET /view/ACME/job/ACME-Pipeline/wfapi/runs from 10.x.x.x : RequestHandlerThreadx" See attachment threaddump-anonymized.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Reinhold Füreder Attachment: threaddump-anonymized.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Thomas Becker commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Sam Van Oort 2.53 is installed and running. Will get back to you if a deadlock occurs and if none occurs within a couple of days as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort updated JENKINS-51132 Thomas Becker Quentin Nerden kutzi I've addressed the deadlock noted in the comments above and released as workflow-cps 2.53 – can you guys install the update? I've done some testing and beyond scrutinizing the code am not seeing any deadlocks, but those tend to be hard to reproduce outside of a real-world context. If there are any issues, please open new issues (just so it's not lost in the noise of the comments). Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: In Review Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java http://jenkins-ci.org/commit/workflow-cps-plugin/c9188cfa5789ea18ee8f4d44bf136f3b72c8cddc Log: Fix additional deadlocks from JENKINS-51132 by ensuring we separate locks on the execution from the run Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort edited a comment on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads [~tbecker] [~qnerden] [~kutzi] I've got a PR up at https://github.com/jenkinsci/workflow-cps-plugin/pull/226 that should cover deadlocks (assuming there aren't more lurking -- I'm checking into one risk in workflow-job before considering it all-clear). Edit: Would appreciate if you guys could give it a shot and confirm it solves issues, since the deadlocks aren't generally reproducible. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Thomas Becker Quentin Nerden kutzi I've got a PR up at https://github.com/jenkinsci/workflow-cps-plugin/pull/226 that should cover deadlocks (assuming there aren't more lurking – I'm checking into one risk in workflow-job before considering it all-clear). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort started work on JENKINS-51132 Change By: Sam Van Oort Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort updated JENKINS-51132 Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort reopened an issue Re-opening due a second deadlock with copyLogs... could be a second JIRA but, eh, I'd rather spend time fixing it than JIRA-wrangling. Working on a fix – somewhat delayed by work travel but should have something soon. Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Resolution: Done Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Basil Crow commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Is there the equivalent of an "LTS train" for plugins like this? I realize that there is no official LTS cycle for plugins, but plugins like this are so tied to core functionality that they seem almost indistinguishable from Jenkins core from my perspective. I genuinely do want to keep everything up-to-date with latest LTS releases and bug fixes, but it can be hard for me to identify what is considered stable and what isn't. I'm glad I read this bug before upgrading to 2.52, because it doesn't seem stable yet. But there's no way I would have known this if I hadn't been reading the release notes very carefully. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Quentin Nerden edited a comment on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Confirmed, 2.52 has issues and 2.49 works without deadlocks. Is there a new bug we could subscribe to? [~svanoort] Or can we reopen this bug? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Thomas Becker commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads And another confirmation for kutzi's deadlock. Am seeing the exact same thing: "Handling GET /manage from 10.242.50.62 : RequestHandlerThread[#165] Jenkins/manage.jelly Jenkins/sidepanel.jelly View/sidepanel.jelly": waiting to lock monitor 0x7f519c48d638 (object 0xc783b328, a org.jenkinsci.plugins.workflow.job.WorkflowRun), which is held by "WorkflowRun.copyLogs [#1] (logIQ #2230)" "WorkflowRun.copyLogs [#1] (logIQ #2230)": waiting to lock monitor 0x7f519c48ba08 (object 0xc783afd0, a org.jenkinsci.plugins.workflow.cps.CpsFlowExecution), which is held by "Running CpsFlowExecution[Owner[logIQ/2230:logIQ #2230]]" "Running CpsFlowExecution[Owner[logIQ/2230:logIQ #2230]]": waiting to lock monitor 0x7f519c48d638 (object 0xc783b328, a org.jenkinsci.plugins.workflow.job.WorkflowRun), which is held by "WorkflowRun.copyLogs [#1] (logIQ #2230)" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Quentin Nerden commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Confirmed, 2.52 has issues and 2.49 works without deadlocks. Is there a new bug we could subscribe to? Or can we reopen this bug? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Thomas Rucker commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I can confirm there's still a deadlock in 2.52 like kutzi mentions. The only option for now seems downgrading to 2.49. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi edited a comment on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I did already update to workflow-cps 2.5.2, but then tomorrow this morning got a new deadlock. See attachment [^deadlock.txt] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I did already update to workflow-cps 2.5.2, but then tomorrow got a new deadlock. See attachment deadlock.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title kutzi updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: kutzi Attachment: deadlock.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Shannon Kerr commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Thank you Sam Van Oort for your quick action. We'll wait for chanti vlad's reported deadlock to be resolved before upgrading. Our downgrade did resolve our issues, as expected. Excellent community work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Awesome chanti vlad that's a second, unrelated deadlock – looking into it and should have a fix soon, but may take a little while to get it reviewed for release (most of the core Pipeline team is travelling or on weekend). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title chanti vlad updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: chanti vlad Comment: I was affected by this. Installing Pipeline: Groovy 2.52 did not fix my symptoms:`May 05, 2018 1:57:17 PM jenkins.metrics.api.Metrics$HealthChecker executeWARNING: Some health checks are reporting as unhealthy: [thread-deadlock : [Running CpsFlowExecution[Owner[MY_PIPELINE_JOB/7521:MY_PIPELINE_JOB #7521]] locked on org.jenkinsci.plugins.workflow.job.WorkflowRun@232fe592 (owned by WorkflowRun.copyLogs [#4] (MY_PIPELINE_JOB #7521)): at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1245) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.saveOwner(CpsFlowExecution.java:1925) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.saveExecutionIfDurable(CpsFlowExecution.java:1906) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.removeHead(CpsFlowExecution.java:1082) at org.jenkinsci.plugins.workflow.cps.FlowHead.remove(FlowHead.java:177) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.subsumeHead(CpsFlowExecution.java:1097) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:436) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:395) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:909) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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), WorkflowRun.copyLogs [#4] (MY_PIPELINE_JOB #7521) locked on org.jenkinsci.plugins.workflow.cps.CpsFlowExecution@757d1262 (owned by Running CpsFlowExecution[Owner[MY_PIPELINE_JOB/7521:MY_PIPELINE_JOB #7521]]): at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal(CpsFlowExecution.java:1603) at hudson.util.XStream2$AssociatedConverterImpl.marshal(XStream2.java:461) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title chanti vlad commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads I was affected by this. Installing Pipeline: Groovy 2.52 did not fix my symptoms: `May 05, 2018 1:57:17 PM jenkins.metrics.api.Metrics$HealthChecker execute WARNING: Some health checks are reporting as unhealthy: [thread-deadlock : [Running CpsFlowExecution[OwnerMY_PIPELINE_JOB/7521:MY_PIPELINE_JOB #7521] locked on org.jenkinsci.plugins.workflow.job.WorkflowRun@232fe592 (owned by WorkflowRun.copyLogs 4 (MY_PIPELINE_JOB #7521)): at org.jenkinsci.plugins.workflow.job.WorkflowRun.save(WorkflowRun.java:1245) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.saveOwner(CpsFlowExecution.java:1925) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.saveExecutionIfDurable(CpsFlowExecution.java:1906) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.removeHead(CpsFlowExecution.java:1082) at org.jenkinsci.plugins.workflow.cps.FlowHead.remove(FlowHead.java:177) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.subsumeHead(CpsFlowExecution.java:1097) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:436) at org.jenkinsci.plugins.workflow.cps.CpsStepContext$2.onSuccess(CpsStepContext.java:395) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:909) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) , WorkflowRun.copyLogs 4 (MY_PIPELINE_JOB #7521) locked on org.jenkinsci.plugins.workflow.cps.CpsFlowExecution@757d1262 (owned by Running CpsFlowExecution[OwnerMY_PIPELINE_JOB/7521:MY_PIPELINE_JOB #7521]): at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal(CpsFlowExecution.java:1603) at hudson.util.XStream2$AssociatedConverterImpl.marshal(XStream2.java:461) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort closed an issue as Done Fixed as of 2.52 release, thanks to a fortuitous community contributor who had already done the investigation. Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Regression appears to be caused by the ReadWrite locks around the TimingFlowNodeStorage in https://github.com/jenkinsci/workflow-cps-plugin/pull/223 using a different locking order. So, that PR fixed a threading issue (ConcurrentModificationException around the FlowNodes) and introduced another one via the fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Nevermind a community contributor seems to have correctly identified what seems like the only plausible cause and submitted a working PR that should fix it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Labels: deadlock regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Sam Van Oort Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Sam Van Oort commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Shannon Kerr Could be we have a deadlock somewhere or thread contention – the existing threading model was full of race conditions but the synchronization may be too agressive. Shannon Kerr Björn Pedersen could we please get a full thread dump attached to this ticket from while the issue is occurring? The one that is attached doesn't include the locks. The Support core plugin is probably the easiest way to do that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Shannon Kerr commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads We're seeing the same behavior. Just downgraded workflow-cps and workflow-job, which we hope resolves the issue. Sam Van Oort is the related to your fixes in https://issues.jenkins-ci.org/browse/JENKINS-50888? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19.2 current requests [ !https://forge.frm2.tum.de/jenkins/monitoring?resource=hourglass.png|width=16,height=16! View in a new page|https://host/jenkins/monitoring?part=currentRequests] !https://host/jenkins/monitoring?resource=bullets/minus.png|id=contextDetailshttp28023Img! Details || Thread|| Request|| Elapsed time (ms)|| Mean time (ms)|| Cpu time (ms)|| Mean cpu time (ms)|| Executed method|| Kill|||Handling GET /jenkins/view/NICOS/job/NicosPipelineDocker/wfapi/runs from xxx.xx.xx. : RequestHandlerThread[#6]| [/view/NICOS/job/NicosPipelineDocker/wfapi/runs?since=%235853=true&_=1525424331349 ajax GET| 226,453|108|8|18|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">|Handling GET /jenkins/ from xxx.xxx.xxx..xxx : RequestHandlerThread[#46] View/index.jelly View/sidepanel.jelly ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly| [/ GET|https://forge.frm2.tum.de/jenkins/monitoring?part=graph=http9b051a0212745888c373b46ee5f27d9d6d905d45]|!https://forge.frm2.tum.de/jenkins/monitoring?resource=dbweb.png|width=16,height=16! 108,266|9,526|61|8,280|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">h3. !https://forge.frm2.tum.de/jenkins/monitoring?resource=systeminfo.png! Add Comment
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen updated an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Change By: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19.2 current requests [!/host/jenkins/monitoring?resource=pdf.png! PDF|https://hostjenkins/monitoring?part=currentRequests=pdf] [ !https://forge.frm2.tum.de/jenkins/monitoring?resource=hourglass.png|width=16,height=16! View in a new page|https://host/jenkins/monitoring?part=currentRequests] !https://host/jenkins/monitoring?resource=bullets/minus.png|id=contextDetailshttp28023Img! Details || Thread|| Request|| Elapsed time (ms)|| Mean time (ms)|| Cpu time (ms)|| Mean cpu time (ms)|| Executed method|| Kill|||Handling GET /jenkins/view/NICOS/job/NicosPipelineDocker/wfapi/runs from xxx.xx.xx. : RequestHandlerThread[#6]| [/view/NICOS/job/NicosPipelineDocker/wfapi/runs?since=%235853=true&_=1525424331349 ajax GET| 226,453|108|8|18|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">|Handling GET /jenkins/ from xxx.xxx.xxx..xxx : RequestHandlerThread[#46] View/index.jelly View/sidepanel.jelly ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly| [/ GET|https://forge.frm2.tum.de/jenkins/monitoring?part=graph=http9b051a0212745888c373b46ee5f27d9d6d905d45]|!https://forge.frm2.tum.de/jenkins/monitoring?resource=dbweb.png|width=16,height=16! 108,266|9,526|61|8,280|org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getCurrentHeads([CpsFlowExecution.java:962|https://forge.frm2.tum.de/jenkins/monitoring?part=source=org.jenkinsci.plugins.workflow.cps.CpsFlowExecution#962])|[!https://forge.frm2.tum.de/jenkins/monitoring?resource=stop.png|width=16,height=16!|https://forge.frm2.tum.de/jenkins/monitoring?action="">h3. !https://forge.frm2.tum.de/jenkins/monitoring?resource=systeminfo.png! Add Comment
[JIRA] (JENKINS-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Björn Pedersen created an issue Jenkins / JENKINS-51132 workflow blocks on cps.CpsFlowExecution.getCurrentHeads Issue Type: Bug Assignee: Unassigned Attachments: st1.log Components: workflow-cps-plugin, workflow-job-plugin Created: 2018-05-04 09:54 Environment: jenkins 2.118 / 2.119 workflow-cps 2.51 workflow-jobs 2.21 Priority: Minor Reporter: Björn Pedersen After some time, jenkins hangs on workflow-related requests: This occured after an update of workflow-cps from 2.49 and workflow-jobs from 2.19. 2 current requests Unable to render embedded object: File (/host/jenkins/monitoring?resource=pdf.png) not found. PDF [ View in a new page|https://host/jenkins/monitoring?part=currentRequests] Details Thread Request Elapsed time (ms) Mean time (ms) Cpu time (ms) Mean cpu time (ms)
