Generating a Thread Dump

Windows Environment

JIRA running from startup.bat

1. In the Command Console window where JIRA is running, open the properties dialog box by right clicking on the title bar and select "Properties".
2. Select the Layout tab.
3. Under Screen Buffer Size, set the Height to 3000.
   
4. Click OK.
5. With the same command console in focus, press CTRL-BREAK. This will output the thread dump to the command console.
6. Scroll back in the command console until you reach the line containing "Full thread dump".
7. Right click the title bar and select Edit -> Mark. Highlight the entire text of the thread dump.
8. Right click the title bar and select Edit -> Copy. The thread dump can then be pasted into a text file.
   

JIRA running as a Windows Service

Using jstack

The JDK ships with a tool named jstack for generating thread dumps.

1. Identify the process. Launch the task manager by, pressing Ctrl + Shift + Esc and find the Process ID of the Java (JIRA) process. You may need to add the PID column using View -> Select Columns ...
2. Run jstack <pid> to Capture a Single Thread Dump. This command will take one thread dump of the process id <pid>, in this case the pid is 22668:

C:\Users\Administrator>jstack.exe -l 22668 > threaddump.txt

This will output a file called threaddump.txt to your current directory.

Linux/Unix/OS X Environment

Linux/Unix Command Line

1. Identify the java process that JIRA is running in. This can be achieved by running a command similar to:

   ps -ef | grep java

   The process will appear similarly as follows:

   keithb     910   873  1 17:01 pts/3    00:00:18 /usr/java/jdk/bin/java -Xms128m -Xmx256m
   -Xms128m -Xmx256m -Djava.awt.headless=true -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
   -Djava.awt.headless=true -Djava.endorsed.dirs=/tmp/atlassian-jira-enterprise-3.6-standalone/common/endorsed
   -classpath :

2. In order to retrieve the thread dump, execute the command

   kill -3 <pid>

   where pid is the process id — in this case, 910.

3. The thread dump will be written to the Tomcat console output. The console output is redirected to the logs/catalina.out file, which can be found in the JIRA Installation Directory for JIRA Standalone / Installer, or for JIRA WAR, under the Tomcat installation directory.

Linux/Unix Alternative: Using jstack and top

Please see Troubleshooting Jira performance with Thread dumps for a way to combine both top and jstack to provide the CPU output of individual threads along with their stack trace.

Linux/Unix Alternative: Generating Thread Dumps using jstack

If you have trouble using kill -3 <pid> to obtain a thread dump, try using jstack a java utility that will output stack traces of Java threads for a given process.

1. Identify the javaprocess that JIRA is running in. This can be achieved by running a command similar to:

   ps -ef | grep java

2. The process will appear similarly as follows:

   adam 22668 0.3 14.9 1691788 903928 ? Sl Jan27 9:36 /usr/lib/jvm/java-6-sun-1.6.0.14/bin/java -Djava.util.logging.config.file=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/conf/logging.properties -XX:MaxPermSize=256m -Xms128m -Xmx1048m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -Datlassian.mail.senddisabled=false -Datlassian.mail.fetchdisabled=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/common/endorsed -classpath /home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/bin/bootstrap.jar -Dcatalina.base=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone -Dcatalina.home=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone -Djava.io.tmpdir=/home/adam/Products/installs/atlassian-jira-enterprise-4.0.1-standalone/temp org.apache.catalina.startup.Bootstrap start
   

3. Run jstack <pid> to Capture a Single Thread Dump
   This command will take one thread dump of the process id <pid>, in this case the pid is 22668, and log output to the file JIRAthreaddump.txt

   adam@jiratrack:~$ jstack 22668 > JIRAthreaddump.txt
   

4. Take Multiple Thread Dumps
   Typically you'll want to take several dumps about 10 seconds apart, in which case you can generate several dumps and output the stack traces to a single file as follows:

   adam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txt
   adam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txt
   adam@jiratrack:~$ jstack 22668 >> JIRAthreaddump.txt
   

   If you are connecting to the server through RDP, jstack might fail with following error:

   Not enough storage is available to process this command 

   You will need to open a RDP session in console mode: mstsc /admin

Analysis Tools

Try TDA or Samurai to inspect your thread dump.

TDA

1. Download TDA
2. CD to the directory where the JAR exists

3. Run:

   java -jar -Xmx512M ~/tda-bin-1.6/tda.jar
   

4. Open your catalina.out file, containing the thread dump

Check the known thread dump knowledge base articles:

• Page:
  Slow performance and "dangerous use of multiple connections" error in Jira
• Page:
  Jira Server / Data Center crashes with OutofMemory Java heap space error
• Page:
  OutOfMemory or Poor Performance due to XML View of a Filter
• Page:
  How to ignore updates in the issues that were made during the weekend while closing them via Automation for Jira
• Page:
  JIRA Deadlocks when Running Tomcat 6.0.24