[JENKINS-32152] java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)

Type: Bug
Resolution: Fixed
Priority: Blocker
Component/s: core
Labels:
- Build
- BuildExecutor
- BuildNumber
- DEAD
- Promotions
Environment:
Jenkins ver. 1.642, Windows Server 2008 R2 Standard

Similar Issues:
Powered by SuggestiMate

Show

Jenkins ver. 1.642

This is occuring on freestyle builds that are triggered by a cron expression and an upstream job (promotions plugin). When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateExceptionThese are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
at hudson.model.RunMap.put(RunMap.java:188)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
at hudson.model.Executor$1.call(Executor.java:364)
at hudson.model.Executor$1.call(Executor.java:346)
at hudson.model.Queue._withLock(Queue.java:1405)
at hudson.model.Queue.withLock(Queue.java:1270)
at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Similar threads:
https://issues.jenkins-ci.org/browse/JENKINS-29268 [Configuration race condition]
https://issues.jenkins-ci.org/browse/JENKINS-26582 [also has this issue for ver 1.621]

Any idea for resolving this issue, we are constantly getting the executer failures states.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

Dead Executor.png
11 kB
2015-12-21 07:51

Riddhi Sharma created issue - 2015-12-21 07:55

Riddhi Sharma made changes - 2015-12-21 07:57

Description

Original: Jenkins ver. 1.642

These are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a sub job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Previous thread: https://issues.jenkins-ci.org/browse/JENKINS-26582 also has this issue for ver 1.621.

Any idea for resolving this issue, we are constantly getting the executer failures states.

New: Jenkins ver. 1.642

These are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Previous thread: https://issues.jenkins-ci.org/browse/JENKINS-26582 also has this issue for ver 1.621.

Any idea for resolving this issue, we are constantly getting the executer failures states.

Riddhi Sharma made changes - 2015-12-21 07:57

Priority

Original: Minor [ 4 ]

New: Blocker [ 1 ]

Riddhi Sharma made changes - 2015-12-21 08:05

Summary

Original: at hudson.model.RunMap.put(RunMap.java:188) -

New: at hudson.model.RunMap.put(RunMap.java:188)

Riddhi Sharma made changes - 2015-12-21 08:09

Description

Original: Jenkins ver. 1.642

These are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Previous thread: https://issues.jenkins-ci.org/browse/JENKINS-26582 also has this issue for ver 1.621.

Any idea for resolving this issue, we are constantly getting the executer failures states.

New: Jenkins ver. 1.642

This is occuring on freestyle builds that are triggered by a cron expression and an upstream job (promotions plugin). When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateExceptionThese are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Previous thread:
https://issues.jenkins-ci.org/browse/JENKINS-29268 [Configuration race condition]
https://issues.jenkins-ci.org/browse/JENKINS-26582 [also has this issue for ver 1.621]

Any idea for resolving this issue, we are constantly getting the executer failures states.

Riddhi Sharma made changes - 2015-12-21 08:09

Description

Original: Jenkins ver. 1.642

This is occuring on freestyle builds that are triggered by a cron expression and an upstream job (promotions plugin). When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateExceptionThese are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Previous thread:
https://issues.jenkins-ci.org/browse/JENKINS-29268 [Configuration race condition]
https://issues.jenkins-ci.org/browse/JENKINS-26582 [also has this issue for ver 1.621]

Any idea for resolving this issue, we are constantly getting the executer failures states.

New: Jenkins ver. 1.642

This is occuring on freestyle builds that are triggered by a cron expression and an upstream job (promotions plugin). When those triggers both happen close to each other it seams to "kill" the executor due to the IllegalStateExceptionThese are newer builds (#533, #532) but still its trying to run the [JobName]\builds\405 ,which already exists. Normally, it should trigger #533, #532 newer jobs IDs. We are constantly able to reproduce the issue every time a child job is triggered by the parent job using "Trigger call/builds on another projects" feature.

Exception:

java.lang.IllegalStateException: C:\Program Files (x86)\Jenkins\jobs\[JobName]\builds\405 already existed; will not overwrite with [JobName] #405
        at hudson.model.RunMap.put(RunMap.java:188)
        at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:176)
        at hudson.model.AbstractProject.newBuild(AbstractProject.java:1019)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1210)
        at hudson.model.AbstractProject.createExecutable(AbstractProject.java:145)
        at hudson.model.Executor$1.call(Executor.java:364)
        at hudson.model.Executor$1.call(Executor.java:346)
        at hudson.model.Queue._withLock(Queue.java:1405)
        at hudson.model.Queue.withLock(Queue.java:1270)
        at hudson.model.Executor.run(Executor.java:346)

Jenkins in 1.607 (2015/03/30) - Has changes which removes race condition rendering the list of executors (issue 27564) might be causing this race condition issue.

Similar threads:
https://issues.jenkins-ci.org/browse/JENKINS-29268 [Configuration race condition]
https://issues.jenkins-ci.org/browse/JENKINS-26582 [also has this issue for ver 1.621]

Any idea for resolving this issue, we are constantly getting the executer failures states.

Riddhi Sharma made changes - 2015-12-21 08:09

Priority

Original: Blocker [ 1 ]

New: Critical [ 2 ]

Riddhi Sharma made changes - 2015-12-21 08:10

Summary

Original: at hudson.model.RunMap.put(RunMap.java:188)

New: java.lang.IllegalStateException: Jenkinsat hudson.model.RunMap.put(RunMap.java:188)

Riddhi Sharma made changes - 2015-12-21 08:11

Summary

Original: java.lang.IllegalStateException: Jenkinsat hudson.model.RunMap.put(RunMap.java:188)

New: java.lang.IllegalStateException: Jenkins\Job\ID already existed; will not overwrite with JobName\ID at hudson.model.RunMap.put(RunMap.java:188)

Riddhi Sharma made changes - 2015-12-21 14:33

Priority

Original: Critical [ 2 ]

New: Blocker [ 1 ]

Assignee:: Riddhi Sharma

Reporter:: Riddhi Sharma

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2015-12-21 07:55

Updated:: 2016-01-20 12:03

Resolved:: 2016-01-20 12:02

Jenkins

Details

Description

Attachments

Attachments

Activity

People

Dates