![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Attachments:
|
java_100CPU_jenkins_dump.tar.gz |
|
Components:
|
core |
|
Created:
|
30/Jul/13 1:03 PM
|
|
Description:
|
The deadlock appears when a few builds are queued up at once. It seems to appear a bit at random, since sometimes all of the jobs can be queued up and built without problems, sometimes Jenkins hangs after 10 builds are queued, sometimes after 80. Therefore I was unable to provide an isolated, reproducible example.
After the deadlock occurs, the java process running jenkins shows up as taking 100% of CPU in "top" console output. It is impossible to get a working HTTP connection to jenkins, "jstack PID" doesn't work as well. However, jstack -F PID and kill -3 PID worked and their output is attached to this report (a bit redundant maybe, especially since I called "kill -3 PID" thrice and probably three dumps are there in stdout log). To kill the java process, "kill -9 PID" was necessary.
|
|
Environment:
|
Most environment details are in file environment.log inside attached tarball. The ones not included there:
* OS: Ubuntu Server 10.04.3 LTS
* RAM: 24 GB
* CPU: Intel Xeon E5620
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
L DоЬrοgοѡѕkі
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
