You use the
jstack command to print Java stack traces of Java threads for a specified Java process. This command is experimental and unsupported. For core files use
This command is experimental and unsupported.
jstack [options] pid
This represents the
jstackcommand-line options. See Options for the jstack Command.
The process ID for which the stack trace is printed. The process must be a Java process. To get a list of Java processes running on a machine, use either the
pscommand or, if the JVM processes are not running in a separate docker instance,jps command.
Note:JDK 10 added support for using the Attach API when attaching to Java processes running in a separate docker process. However, the
jpscommand will not list the JVM processes that are running in a separate docker instance. If you are trying to connect a Linux host with a Virtual Machine that is in a docker container, you must use tools such as
psto look up the PID of the JVM.
jstack command prints Java stack traces of Java threads for a specified Java process. For each Java frame, the full class name, method name, byte code index (BCI), and line number, when available, are printed. C++ mangled names aren’t demangled. To demangle C++ names, the output of this command can be piped to
c++filt. When the specified process is running on a 64-bit JVM, you might need to specify the
-J-d64 option, for example:
jstack -J-d64pid .
This command is unsupported and might not be available in future releases of the JDK. In Windows Systems where the
dbgeng.dll file isn’t present, the Debugging Tools for Windows must be installed so that these tools work. The
PATH environment variable needs to contain the location of the
jvm.dll that is used by the target process, or the location from which the core dump file was produced.