-
Bug
-
Resolution: Fixed
-
Major
-
None
Sometimes when the build node is stressed, the plugin terminates abnormally and kills the executor. Jenkins allows to restart the executor, and then the build process resumes as normal. Unfortunately, the stack trace below is the only evidence I have got:
java.lang.NullPointerException at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.buildsOfProjectOnNode(ThrottleQueueTaskDispatcher.java:121) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canTake(ThrottleQueueTaskDispatcher.java:80) at hudson.model.queue.QueueTaskDispatcher.canTake(QueueTaskDispatcher.java:101) at hudson.model.Queue$JobOffer.canTake(Queue.java:214) at hudson.model.Queue.pop(Queue.java:799) at hudson.model.Executor.grabJob(Executor.java:276) at hudson.model.Executor.run(Executor.java:206)
- is related to
-
JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors
- Resolved