[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Steven Christou assigned JENKINS-18169 to Steven Christou Deadlock when running multiple delete Change By: Steven Christou (04/Jun/14 12:37 AM) Assignee: StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-18169) Deadlock when running multiple delete
Steven Christou assigned JENKINS-18169 to Unassigned Deadlock when running multiple delete Change By: Steven Christou (04/Jun/14 12:37 AM) Assignee: StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [core] (JENKINS-18169) Deadlock when running multiple delete
Antoine Musso commented on JENKINS-18169 Deadlock when running multiple delete I am hit by the same issue with Jenkins 1.509.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson commented on JENKINS-18169 Deadlock when running multiple delete I noticed that this is probably the same as https://issues.jenkins-ci.org/browse/JENKINS-18199 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson updated JENKINS-18169 Deadlock when running multiple delete stack trace shown in Javamelody when deleting logs from two builds in prallel Change By: Marcus Jacobsson (14/Jun/13 6:29 AM) Attachment: build1.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson updated JENKINS-18169 Deadlock when running multiple delete stack trace shown in Javamelody when deleting logs from two builds in prallel Change By: Marcus Jacobsson (14/Jun/13 6:28 AM) Attachment: build2.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Emil Sit updated JENKINS-18169 Deadlock when running multiple delete We have seen this issue as well. We are using Jenkins 1.510. We are using the Job-DSL-Plugin which I believe will bulk delete jobs. Change By: Emil Sit (12/Jun/13 4:10 PM) Attachment: jenkins-18169-thread-dump-redacted.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Emil Sit updated JENKINS-18169 Deadlock when running multiple delete Some further debugging with jstack reveals that there is a deadlock caused by the RenameListener in the Parameterized Trigger plugin. (See attached jstack output.) For each doDelete request that comes in, the thread first holds a lock on itself (via synchronized) in the delete method on Project (extends Job). Each job then winds up calling the RenameListener in the ParameterizedTrigger plugin. The RenameListener iterates over all projects, calling getPublishersList which is also synchronized. When delete A and delete B come in at the same time, job A and B are locked, and then B's RenameListener blocks on A and vice versa. It looks like getPublishersList() is synchronized just for safety in initializing the publishers list. A potential fix might be to use AtomicReference instead. Note that any fix would need to be applied to the other lazy initialized fields in Project (getBuildersList or getBuildWrappersList). Change By: Emil Sit (12/Jun/13 4:44 PM) Attachment: jenkins-18169-jstack-deadlock.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson
created JENKINS-18169
Deadlock when running multiple delete
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
03/Jun/13 6:58 AM
Description:
Tried to remove ~20 builds in parallel with 30 days of build logs (a lot of files) and this resulted in a deadlock and we needed to restart the server.
JavaMelody listed the doDelete threads as deadlocked and showed
1 x hudson.model.Job.delete(Job.java:587)
17 x hudson.model.Project.getPublishersList(Project.java:114)
as a result of the deadlock we can't edit builds anymore
/configSubmit : http-bio-8080-exec-3552 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3503 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3543 yes 5 BLOCKED hudson.model.Job.delete(Job.java:587)
Looking in project.java it looks like a deprecated method is used
/**
* @deprecated as of 1.463 We will be soon removing the restriction that
* only one instance of publisher is allowed per type. Use
* {@link #getPublishersList()} instead.
*/
public MapDescriptorPublisher,Publisher getPublishers() {
return publishers.toMap();
}
Environment:
Jenkins 1.509.1 running on Ubuntu 12.04 with JDK 1.7
Project:
Jenkins
Priority:
Major
Reporter:
Marcus Jacobsson
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-18169) Deadlock when running multiple delete
kutzi commented on JENKINS-18169 Deadlock when running multiple delete Please attach the full thread dump! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
