1jstack(1)                   General Commands Manual                  jstack(1)
2
3
4

Name

6       jstack - Stack Trace
7
8

SYNOPSIS

10       jstack [ option ] pid
11       jstack [ option ] executable core
12       jstack [ option ] [server-id@]remote-hostname-or-IP
13
14

PARAMETERS

16       Options  are mutually exclusive. Option, if used, should follow immedi‐
17       ately after the command name. See OPTIONS.
18
19          pid
20             process id for which the  stack  trace  is  to  be  printed.  The
21             process  must  be a Java process. To get a list of Java processes
22             running on a machine, jps(1) may be used.
23
24
25          executable
26             Java executable from which the core dump was produced.
27
28          core
29             core file for which the stack trace is to be printed.
30
31          remote-hostname-or-IP
32             remote debug server's (see jsadebugd(1)) hostname or IP address.
33
34          server-id
35             optional unique id, if multiple debug servers are running on  the
36             same remote host.
37
38

DESCRIPTION

40       jstack  prints  Java  stack  traces  of  Java  threads for a given Java
41       process or core file or a remote debug server. For each Java frame, the
42       full  class name, method name, 'bci' (byte code index) and line number,
43       if available, are printed. With the -m option, jstack prints both  Java
44       and native frames of all threads along with the 'pc' (program counter).
45       For each native frame, the closest native symbol to 'pc', if available,
46       is printed. C++ mangled names are not demangled. To demangle C++ names,
47       the output of this command may  be  piped  to  c++filt.  If  the  given
48       process  is  running on a 64-bit VM, you may need to specify the -J-d64
49       option, e.g.:
50
51
52       jstack -J-d64 -m pid
53
54
55       NOTE - This utility is unsupported and may or may not be  available  in
56       future  versions of the JDK. In Windows Systems where dbgeng.dll is not
57       present, 'Debugging Tools For Windows' needs to be  installed  to  have
58       these tools working. Also, PATH environment variable should contain the
59       location of jvm.dll used by the target process  or  the  location  from
60       which the Crash Dump file was produced.
61
62       For example, set PATH=<jdk>\jre\bin\client;%PATH%
63

OPTIONS

65          -F Force a stack dump when 'jstack [-l] pid' does not respond.
66
67          -l Long  listing.  Prints additional information about locks such as
68             list of owned java.util.concurrent ownable synchronizers @
69             http://docs.oracle.com/javase/7/docs/api/java/util/concur‐
70             rent/locks/AbstractOwnableSynchronizer.html.
71
72          -m prints mixed mode (both Java and native C/C++ frames) stack
73             trace.
74
75          -h prints a help message.
76
77          -help
78             prints a help message
79
80

SEE ALSO

82          o pstack(1)
83
84          o c++filt(1)
85
86          o jps(1)
87
88          o jsadebugd(1)
89
90

KNOWN BUGS

92       Mixed mode stack trace, the -m option, does not work with the remote
93       debug server.
94
95                                  16 Mar 2012                        jstack(1)