jstack | Display stack traces for a Java process
|
Synopsis
jstack [ options ] pid // local process
jstack [ options ] executable core // core file
jstack [ options ] [process-name@]hostname // remote process
Description
jstack
prints
stack traces for each of the Java threads running in the specified
Java process. jstack can be started in three
ways:
Specify the process id of a Java process running locally to obtain
configuration information about it. See jps to
list local processes. To obtain post-mortem configuration information from a core file,
specify the Java executable that produced the core file and the core
file itself on the command line. To obtain configuration information about a Java process running
remotely, specify the name of the remote host, optionally prefixed by
a remote process name and @ sign. jsadebugd must
be running on the remote host.
In Java 5.0, jstack is experimental,
unsupported, and not available on all platforms.
Options
- -help, -h
-
Prints a help message.
- -m
-
Displays stack traces in "mixed
mode," that is, displays both Java and native method
stack frames. Without this option, the default is to display Java
stack frames only.
See also
jps, jsadebugd
|