1JSTACK(1) JDK Commands JSTACK(1)
2
3
4
6 jstack - print Java stack traces of Java threads for a specified Java
7 process
8
10 Note: This command is experimental and unsupported.
11
12 jstack [options] pid
13
14 options
15 This represents the jstack command-line options. See Options
16 for the jstack Command.
17
18 pid The process ID for which the stack trace is printed. The
19 process must be a Java process. To get a list of Java processes
20 running on a machine, use either the ps command or, if the JVM
21 processes are not running in a separate docker instance, the jps
22 command.
23
25 The jstack command prints Java stack traces of Java threads for a spec‐
26 ified Java process. For each Java frame, the full class name, method
27 name, byte code index (BCI), and line number, when available, are
28 printed. C++ mangled names aren't demangled. To demangle C++ names,
29 the output of this command can be piped to c++filt. When the specified
30 process is running on a 64-bit JVM, you might need to specify the
31 -J-d64 option, for example: jstack -J-d64 pid.
32
33 Note:
34
35 This command is unsupported and might not be available in future re‐
36 leases of the JDK. In Windows Systems where the dbgeng.dll file isn't
37 present, the Debugging Tools for Windows must be installed so that
38 these tools work. The PATH environment variable needs to contain the
39 location of the jvm.dll that is used by the target process, or the lo‐
40 cation from which the core dump file was produced.
41
43 -l The long listing option prints additional information about
44 locks.
45
46 -h or -help
47 Prints a help message.
48
49
50
51JDK 16 2021 JSTACK(1)