This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

If Bamboo stops responding, or is performing poorly, you should create a thread dump to help Atlassian determine the cause of the problem.

This will show the state of each thread in the JVM, including a stack trace and information about what locks that thread is holding and waiting for. 

Linux (and Solaris and other Unixes) Users

Find the process id of the JVM and issue the command:

Use the ps command to get list of all processes.

kill -3 <pid>

Note: This will not kill your server (so long as you included the "-3" option, no space in between).
The thread dump will be printed to Bamboo's standard output.

Please note that some application servers (like tomcat) redirect stdout (to catalina.out for instance).

Jstack (any Platform with an JAVA JDK)

Sun JDK 1.5 and above ship with native tool called jstack to perform thread dump. To use the tool find the Proccess ID and execute the command:

jstack <ProccessID>

Thread Dump Tools

  • No labels

1 Comment

  1. Charles Albrecht

    Mar 04, 2010

    Also available is $JAVA_HOME/bin/jstack, which prints stack results to STDOUT for the invoking process.

      $JAVA_HOME/bin/jstack <pid>

    I've never had particularly good luck with the kill -3 <pid> approach in a production environment (launching with bamboo.sh console).



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.