[JIRA] [external-resource-dispatcher-plugin] (JENKINS-32917) Locked resource in use by multiple jobs
Title: Message Title Jonathan Strickland edited a comment on JENKINS-32917 Re: Locked resource in use by multiple jobs Running Core Jenkins 1.651Externeral Dispatcher: 1.1.0 Just started hitting this issue just recently as we are expanding our pipelines and resources. From reviewing the code (very briefly), I don't see anywhere that would prevent multiple threads obtaining the resource lock at the same time. Following the code from https://github.com/jenkinsci/external-resource-dispatcher-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/ExternalResourceQueueTaskDispatcher.java#L113 to https://github.com/jenkinsci/external-resource-dispatcher-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/ResourceMonitorExternalResourceManager.java#L203 there appear to be multiple places that could have mutual exclusion problems. Perhaps the job dispatcher in Jenkins runs in a single thread; but I would have to review the architecture to be certain and from what is being observed this may not be the case.The really unfortunate part of this and any mutual exclusion problem is I turned on full logging to observe the behavior and it went away. I'm going to fork this off and see if we can propose a possible fix. Unless, the Queue handler in Jenkins is itself running in a single thread. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-resource-dispatcher-plugin] (JENKINS-32917) Locked resource in use by multiple jobs
Title: Message Title Jonathan Strickland commented on JENKINS-32917 Re: Locked resource in use by multiple jobs Just started hitting this issue just recently as we are expanding our pipelines and resources. From reviewing the code (very briefly), I don't see anywhere that would prevent multiple threads obtaining the resource lock at the same time. Following the code from https://github.com/jenkinsci/external-resource-dispatcher-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/ExternalResourceQueueTaskDispatcher.java#L113 to https://github.com/jenkinsci/external-resource-dispatcher-plugin/blob/master/src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/resourcemanagers/ResourceMonitorExternalResourceManager.java#L203 there appear to be multiple places that could have mutual exclusion problems. Perhaps the job dispatcher in Jenkins runs in a single thread; but I would have to review the architecture to be certain and from what is being observed this may not be the case. The really unfortunate part of this and any mutual exclusion problem is I turned on full logging to observe the behavior and it went away. I'm going to fork this off and see if we can propose a possible fix. Unless, the Queue handler in Jenkins is itself running in a single thread. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-resource-dispatcher-plugin] (JENKINS-32917) Locked resource in use by multiple jobs
Title: Message Title Jan Hollevoet created an issue Jenkins / JENKINS-32917 Locked resource in use by multiple jobs Issue Type: Bug Assignee: Jan Hollevoet Components: external-resource-dispatcher-plugin Created: 12/Feb/16 3:07 PM Priority: Major Reporter: Jan Hollevoet I frequently see two jobs using the same resource, whereas only one job has actually locked the resource. These jobs all have a SCM configured. I suspect that the locking occurs too late (only after the check out). So, while the first job is updating the workspace the resource is not locked yet and the other job thinks he can use that same resource. Add Comment
