-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Jenkins master with at least two agents
-
-
2.204
When an implementation of NodeProperty or QueueTaskDispatcher throws an exception and Jenkins is using two or more agents, the queue stops moving the tasks because the maintain method ends unexpectedly.
- is caused by
-
JENKINS-59844 Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
-
- Reopened
-
I link to JENKINS-59844 because it is the issue that discovers this one. A NodeProperty implementer was calling the ProcessBuilder#_start method (JDK) with an empty command, therefore throwing an _IndexOutOfBoundExceptions and hanging the queue. Every job reviewed in the Queue#maintain method after this event is not managed because the method ends abruptly.