[JIRA] (JENKINS-40757) Thread has died in all executors

12 views
Skip to first unread message

m.deepanchakravarthy@gmail.com (JIRA)

unread,
Jan 3, 2017, 12:31:01 AM1/3/17
to jenkinsc...@googlegroups.com
DeepanChakravarthy Murugesan created an issue
 
Jenkins / Bug JENKINS-40757
Thread has died in all executors
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2017/Jan/03 5:30 AM
Environment: Jenkins ver. 1.606 windows 7
Labels: deadlock
Priority: Blocker Blocker
Reporter: DeepanChakravarthy Murugesan

We are getting "Thread has died" issue in all our executors and this leads to block our daily activities. When I clicked on "Restart the thread" it looks the error went off, but when I start a job to run, the executor gives the same error.
Below is the Jenkins logs

java.lang.IllegalStateException: C:_Harman_NA_Info\ALM\Jenkins\master\jobs\HLF_All_Projects_All_Tasks\builds\811 already existed; will not overwite with HLF_All_Projects_All_Tasks #811
at hudson.model.RunMap.put(RunMap.java:187)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1006)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)

I tired with "set next build number" plugin to set the build number manually, but no improvement. Could you please help in this issue?

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

dbeck@cloudbees.com (JIRA)

unread,
Jan 3, 2017, 7:30:01 AM1/3/17
to jenkinsc...@googlegroups.com
Daniel Beck resolved as Not A Defect
 
  • Issue does not contain enough information to investigate further.
  • The Jenkins version is almost two years outdated, needs to happen on a current release for us to care
  • Looks more like a support request than a bug report.
Change By: Daniel Beck
Status: Open Resolved
Resolution: Not A Defect
Reply all
Reply to author
Forward
0 new messages