jmap - Memory Map


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


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

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 may be used.

Java executable from which the core dump was produced.

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

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

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


jmap prints shared object memory maps or heap memory details of a given process or core file or a remote debug server.

NOTE - This utility is unsupported and may or may not be available in future versions of the J2SE SDK.
jmap is not currently available on Windows platforms or on the Linux Itanium platform.


<no option>
When no option is used jmap prints shared object mappings. For each shared object loaded in the target VM, start address, the size of the mapping, and the full path of the shared object file are printed. This is similar to the Solaris pmap utility.
Prints a heap summary. GC algorithm used, heap configuration and generation wise heap usage are printed.
Prints a histogram of the heap. For each Java class, number of objects, memory size in bytes, and fully qualified class names are printed. VM internal class names are printed with '*' prefix.
Prints class loader wise statistics of permanent generation of Java heap. For each class loader, its name, liveness, address, parent class loader, and the number and size of classes it has loaded are printed.
Prints a help message.

Prints a help message.


Copyright © 2004 Sun Microsystems, Inc. All Rights Reserved.

Java Software