1.509.x is too old for anyone to still care. Can you reproduce the issue on 1.532.x at least?

Unfortunately, I still have to care about it.

The last valuable change in hudson.model.queue.MappingWorksheet was in 1.520, but the most of code (including referenced classes) have not been changed since 2011. I suppose the issue is still active
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/queue/MappingWorksheet.java

BTW, it makes sense to somehow reproduce it in unit tests

Just meant that this won't get much love here, given it's out of community support, unless you can show it's happening in newer Jenkins versions.

If it's possible to set up a Jenkins using specific steps and reproducible experience the problem, providing these instructions alone would help already IMO.

I've re-assigned the issue to myself.
When I finish other high-priority assignment (seems to be "never ever"), I'll try to create a reproducible scenario for the issue

Hi,

I'm seeing this with an even older version: 1.480.3. The trace is slightly difference, but similar:
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at hudson.model.queue.MappingWorksheet$ReadOnlyList.get(MappingWorksheet.java:102)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.execute(MappingWorksheet.java:150)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.access$000(MappingWorksheet.java:110)
at hudson.model.queue.MappingWorksheet$Mapping.execute(MappingWorksheet.java:298)
at hudson.model.Queue.maintain(Queue.java:1045)
at hudson.model.Queue.pop(Queue.java:863)
at hudson.model.Executor.grabJob(Executor.java:285)
at hudson.model.Executor.run(Executor.java:206)
more info

In particular, the MappingWorksheet bits are the same.

This issue https://issues.jenkins-ci.org/browse/JENKINS-19799 seems to be exactly the same as well, and I agree with the assement made there: if isAvailable is false, there's nothing preventing 'e' to go out of bounds in ExecutorChunk.execute().

Attaching a patch against lastest git

Make sure e doesn't go out of bounds.

Frederik: Please consider submitting a pull request on Github.