jhsdb - attach to a Java process or launch a postmortem debugger to analyze the content of a core dump from a crashed Java Virtual Machine (JVM)
jhsdb clhsdb [--pid pid | --exe executable --core coredump]
jhsdb debugd [options] (pid | executable coredump) [server-id]
jhsdb hsdb [--pid pid | --exe executable --core coredump]
jhsdb jstack [--pid pid | --exe executable --core coredump] [options]
jhsdb jmap [--pid pid | --exe executable --core coredump] [options]
jhsdb jinfo [--pid pid | --exe executable --core coredump] [options]
jhsdb jsnap [options] [--pid pid | --exe executable --core coredump]
The process ID to which the jhsdb tool should attach. The process must be a Java process. To get a list of Java processes running on a machine, use the ps command or, if the JVM processes are not running in a separate docker instance, the jps command.
Note: JDK 10 has added support for using the Attach API when attaching to Java processes running in a separate docker process. However, the jps command 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 ps to look up the PID of the JVM.
jhsdb tool should attach.
jhsdb mode. See Common Options for jhsdb Modes, Options for the debugd Mode, Options for the jinfo Mode, Options for the jmap Mode, Options for the jmap Mode, Options for the jstack Mode, and Options for the jsnap Mode.
Note:
Either the pid or the pair of executable and core files must be provided.
You can use the jhsdb tool to attach to a Java process or to launch a postmortem debugger to analyze the content of a core-dump from a crashed Java Virtual Machine (JVM). This command is experimental and unsupported.
Note:
Attaching the jhsdb tool to a live process will cause the process to hang and the process will probably crash when the debugger detaches.
The jhsdb tool can be launched in any one of the following modes:
jhsdb clhsdbjhsdb debugdjhsdb hsdbjhsdb jstackjhsdb jmapjhsdb jinfojhsdb jsnapIn addition to any required jstack, jmap, jinfo or jsnap mode specific options, the pid, exe, or core options must be provided for all modes. The following options are available for all modes.
--pid--exe--core--helpWithout specified options, the jhsdb jinfo prints both flags and properties.
--flags--syspropsIn addition to the following mode specific options, the pid, exe, or core options described in Common Options for jhsdb Modes must be provided.
pmap.
--heapjava heap summary.
--binaryheapjava heap in hprof binary format.
--dumpfile--histojava object heap.
--clstats--finalizerinfoIn addition to the following mode specific options, the pid, exe, or core options described in Common Options for jhsdb Modes must be provided.
--locksjava.util.concurrent locks information.
--mixedjava and native frames if the platform allows it.
In addition to the following mode specific option, the pid, exe, or core options described in Common Options for jhsdb Modes must be provided.
--all