jmap-java-1.7.0-openjdk-1.7.0.131-2.6.9.0.el7_3.x86_64 (1) Linux Manual Page

jmap – Memory Map

Synopsis

jmap [ option ] pid
jmap [ option ] executable core
jmap [ option ] [server-id@]remote-hostname-or-IP

Parameters

option

Options are mutually exclusive. Option, if used, should follow immediately after the command name.

pid

process id for which the memory map is to be printed. The process must be a Java process. To get a list of Java processes running on a machine, jps(1) may be used.

executable

Java executable from which the core dump was produced.

core

core file for which the memory map is to be printed.

remote-hostname-or-IP

remote debug server’s (see jsadebugd(1)) hostname or IP address.

server-id

optional unique id, if multiple debug servers are running on the same remote host.

Description

jmap prints shared object memory maps or heap memory details of a given process or core file or a remote debug server. If the given process is running on a 64-bit VM, you may need to specify the -J-d64 option, e.g.:

jmap -J-d64 -heap pid

NOTE: This utility is unsupported and may or may not be available in future versions of the JDK. In Windows Systems where dbgeng.dll is not present, ‘Debugging Tools For Windows’ needs to be installed to have these tools working. Also, PATH environment variable should contain the location of jvm.dll used by the target process or the location from which the Crash Dump file was produced.

For example, set PATH=<jdk>\jrein