1JSTACK(1)                        JDK Commands                        JSTACK(1)
2
3
4

NAME

6       jstack  -  print Java stack traces of Java threads for a specified Java
7       process
8

SYNOPSIS

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
24              Note: JDK 10 has added support for using the Attach API when at‐
25              taching to Java processes running in a separate docker  process.
26              However,  the  jps  command will not list the JVM processes that
27              are running in a separate docker instance.  If you are trying to
28              connect  a Linux host with a Virtual Machine that is in a docker
29              container, you must use tools such as ps to look up the  PID  of
30              the JVM.
31

DESCRIPTION

33       The jstack command prints Java stack traces of Java threads for a spec‐
34       ified Java process.  For each Java frame, the full class  name,  method
35       name,  byte  code  index  (BCI),  and  line number, when available, are
36       printed.  C++ mangled names aren't demangled.  To demangle  C++  names,
37       the output of this command can be piped to c++filt.  When the specified
38       process is running on a 64-bit JVM,  you  might  need  to  specify  the
39       -J-d64 option, for example: jstack -J-d64 pid.
40
41       Note:
42
43       This  command  is  unsupported and might not be available in future re‐
44       leases of the JDK.  In Windows Systems where the dbgeng.dll file  isn't
45       present,  the  Debugging  Tools  for  Windows must be installed so that
46       these tools work.  The PATH environment variable needs to  contain  the
47       location  of the jvm.dll that is used by the target process, or the lo‐
48       cation from which the core dump file was produced.
49

OPTIONS FOR THE JSTACK COMMAND

51       -l     The long listing  option  prints  additional  information  about
52              locks.
53
54       -h or -help
55              Prints a help message.
56
57
58
59JDK 14                               2020                            JSTACK(1)