-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Ubuntu, openjdk-7, Jenkins 1.656
Unable to obtain a thread dump when Jenkins is stuck coming up.
According to https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump
you should be able to obtain a thread dump by sending SIGQUIT on the master node. While the PID of Jenkins changes (indicating that SIGQUIT was acted upon), no thread dump is observed on stdout/stderr or /var/log/jenkins/jenkins.log.
Since I am trying to diagnose why the Jenkins takes 2hrs to start up, the /threadDump method in the GUI is not suitable in this case.
- links to
[JENKINS-41457] thread dump via signal not working on master node
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Remote Link | New: This issue links to "CloudBees Internal CJP-6414 (Web Link)" [ 19237 ] |