How to take Thread Dumps from a JVM

http://helpx.adobe.com/experience-manager/kb/TakeThreadDump.html

Question

Answer,
Resolution

Step
1: Get the PID of your java process

Step
2: Request a Thread Dump from the JVM

jstack

jstack
script

Alternative
Ways to Obtain a Thread Dump

Unix,
Mac OSX and Linux (JDK 1.4 or lesser version)

Windows:

JDK
1.X-1.5

JDK
1.6

Applies
to

Question

A thread dump is a list of all the Java threads that are currently active in a Java Virtual Machine (JVM).

How can I take thread dumps from a JVM on Unix or Windows?

Answer, Resolution

There are several ways to take thread dumps from a JVM. It is highly recommended to take more than 1 thread dump. A good practice is to take 10 thread dumps at a regular interval (eg. 1 thread dump every 10 seconds).

Step 1: Get the PID of your java process

The first piece of information you will need to be able to obtain a thread dump is your java process's PID.

The java JDK ships with the jps command which lists all java process ids. You can run this command like this:

jps -l

70660 sun.tools.jps.Jps

70305

Note: In
Linux and UNIX, you may have to run this command as

sudo -u user jps -l

, where "user" is the
username of the user that the java process is running as.

If this doesn't work or you still cannot find your java process, (path not set, JDK not installed, or older Java version), use

UNIX, Linux and Mac OSX:

ps -el | grep java

Windows:

Press

Ctrl+Shift+Esc

to open the task manager and find the PID of the java process

Step 2: Request a Thread Dump from the JVM

jstack

If installed/available, we recommend using the jstack tool. It prints thread dumps to the command line console.

To obtain a thread dump using jstack, run the following command:

jstack <pid>

You can output consecutive thread dumps to a file by using the console output redirect/append directive:

jstack <pid> >> threaddumps.log

Notes:

The jstack tool is available since JDK 1.5 (for JVM on Windows it's available in some versions of JDK 1.5 and JDK 1.6 only).

jstack works even if the

-Xrs

jvm parameter is enabled

It's not possible to use the jstack tool from JDK 1.6 to take threaddumps from a process running on JDK 1.5.

In Linux and UNIX, you may need to run this command as

sudo -u user jstack <pid> >> threaddumps.log

, where "user" is the user that the java process is running as.

In Windows, if you run jstack and get the error "Not enough storage is available to process this command" then you must run jstack as the windows SYSTEM user. You can do this by using psexec which you can download here.
Then you can run jstack like this:

psexec -s jstack <pid> >> threaddumps.log

jstack script

Here's a script, taken from eclipse.org that
will take a series of thread dumps using jstack.

#!/bin/bash

if [ $# -eq 0 ]; then

echo >&2 "Usage: jstackSeries <pid> <run_user> [ <count> [ <delay> ] ]"

echo >&2 " Defaults: count = 10, delay = 0.5 (seconds)"

exit 1

fi

pid=$1 # required

user=$2 # required

count=${3:-10} # defaults to 10 times

delay=${4:-0.5} # defaults to 0.5 seconds

while [ $count -gt 0 ]

do

sudo -u $user jstack -l $pid >jstack.$pid.$(date +%H%M%S.%N)

sleep $delay

let count--

echo -n "."

done

Just run it like this:

sh jstackSeries.sh [pid] [cq5serveruser] [count] [delay]

For example:

sh jstackSeries.sh 1234 cq5serveruser 10 3

1234 is the pid of the java process

cq5serveruser is the Linux or Unix user that the java process runs as

10 is how many thread dumps to take

3 is the delay between each dump):

Alternative Ways to Obtain a Thread Dump

If the jstack tool is not available to you then you can take thread dumps as follows:

Note: Some tools cannot take thread dumps from the JVM if the commandline parameter

-Xrs

is enabled. If you are having trouble taking thread dumps then please see if this option is enabled.

Unix, Mac OSX and Linux (JDK 1.4 or lesser version)

On Unix, Mac OSX and Linux, you can send a QUIT signal to the java process to tell it to output a thread dump to standard output.

Run this command to do this:

kill -QUIT <pid>

You may need to run this command as

sudo -u user kill -QUIT <pid>

where "user" is the user that the java process is running as.

If you are starting CQSE using the

crx-quickstart/server/start

script then your thread dumps will be output to

crx-quickstart/server/logs/startup.log

. If you are using a 3rd party application server such as JBoss,
WebSphere, Tomcat, or other then please see the server's documentation to find out which file the standard output is directed to.


Windows:

JDK 1.X

Download javadump.exe (Attached below)

Start the JVM with these 3 arguments. They must be in the right order.

-XX:+UnlockDiagnosticVMOptions -XX:+LogVMOutput -XX:LogFile=C:\tmp\jvmoutput.log

Press Ctrl+Shift+Esc to open the task manager

Find the PID of the java process

From the command line run

javadump.exe [pid]

The thread dump will appear in the

jvmoutput.log

file mentioned in step 2.


JDK 1.6

Get a thread dump from jconsole tool, by using a plugin : [0]

Here's how you can request a thread dump:

Add the following parameter to the jvm running Communique :

-Dcom.sun.management.jmxremote

Download and install JDK 1.6 (if not done yet)

Download and extract the Thread
Dump Analyzer utility [1]

Run

jconsole.exe

of JDK 1.6

jconsole.exe -pluginpath /path/to/file/tda.jar

Click on the Thread dumps tab

Click on the Request Thread Dump ... link

Note: If you are running CQ5 and or CRX (with Sling) and want to observe the running threads, you can request

http://<host>:<port>/system/console/threads

to get a thread list. However, please note that these thread dumps
will not work with thread dump analysis tools such as samurai or tda