• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • None
    • Jenkins 2.150.2
      Lockable Resources Plugin 2.5

      I got this ConcurrentModificationException when using "lock" step for several pipelines running on the same master at the same time. I believe it can happen when new locks are being created while the list of locks is being looped through.

      java.util.ConcurrentModificationException
      at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909)
      at java.util.ArrayList$Itr.next(ArrayList.java:859)
      at org.jenkins.plugins.lockableresources.LockableResourcesManager.fromName(LockableResourcesManager.java:156)
      at org.jenkins.plugins.lockableresources.queue.LockableResourcesStruct.<init>(LockableResourcesStruct.java:83)
      at org.jenkins.plugins.lockableresources.LockStepExecution.start(LockStepExecution.java:62)
      at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268)
      at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176)
      at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
      at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
      at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
      at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)

          [JENKINS-57727] ConcurrentModificationException from lock step

          James Withers added a comment -

          Getting the same issue for Jenkins 2.190.2 and Lockable Resources Plugin2.7.

          Has happened a few times and seems to be happening when many jobs have started at the same time and they are all trying to use the lock step.

          James Withers added a comment - Getting the same issue for Jenkins 2.190.2 and Lockable Resources Plugin2.7. Has happened a few times and seems to be happening when many jobs have started at the same time and they are all trying to use the lock step.

          Should be fixed in the next release, see https://github.com/jenkinsci/lockable-resources-plugin/pull/191

          Tobias Gruetzmacher added a comment - Should be fixed in the next release, see https://github.com/jenkinsci/lockable-resources-plugin/pull/191

            tgr Tobias Gruetzmacher
            wbrode William Brode
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: