[JIRA] (JENKINS-50138) Job and executor freeze and become zombie due to groovy issue
Title: Message Title Andrew Bayer commented on JENKINS-50138 Re: Job and executor freeze and become zombie due to groovy issue I'm not sure how we can do anything about this at this point - if the Groovy compiler freezes, we can't exactly catch the problem ahead of time, and I'm not sure if we've got a way to kill the frozen thread. But hey, we'll take a look. 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-50138) Job and executor freeze and become zombie due to groovy issue
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50138 Job and executor freeze and become zombie due to groovy issue Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline 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-50138) Job and executor freeze and become zombie due to groovy issue
Title: Message Title
Álvaro Iradier created an issue
Jenkins / JENKINS-50138
Job and executor freeze and become zombie due to groovy issue
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-03-13 11:49
Environment:
Jenkins 2.73.3, Jenkins 2.89.4 LTS, Jenkins 2.111
Priority:
Major
Reporter:
Álvaro Iradier
Related to this issue reported to Groovy team: https://issues.apache.org/jira/browse/GROOVY-8507 The groovyc compiler hangs and freezes if enum is declared nested inside another enum. The problem is, when this happens, the Job and the executor in Jenkins become zombie threads, and they need to be killed by finding the Thread name on the Jenkins console and stopping both the executor and the Job threads, as instructed here: https://stackoverflow.com/questions/14456592/how-to-stop-an-unstoppable-zombie-job-on-jenkins-without-restarting-the-server The red cross icon next to the executor does not cancel the Job. So, I think the processes should not become zombie and impossible to kill, and this situation should be either detected, or allow the user to kill the freezed Job. How to reproduce Simply create a Pipeline type Job, and include the following code in the Pipeline:
enum OuterEnum {
VALUE,
enum InnerEnum {
A
}
}
node {
stage('Break') {
echo '' + "${OuterEnum.values()}"
}
}
The Job and the executor will freeze, and there is no way to kill them from the UI.
