Jmap: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
 
(One intermediate revision by the same user not shown)
Line 17: Line 17:
=Capturing Permanent Generation Info=
=Capturing Permanent Generation Info=


  jmap -permstat JBOSS_PID >& permstat.out
  jmap -permstat JBOSS_PID > permstat.out


=When JVM is too Busy to Allow Sockets=
=When JVM is too Busy to Allow Sockets=
Line 26: Line 26:
  1670: Unable to open socket file: target process not responding or HotSpot VM not loaded
  1670: Unable to open socket file: target process not responding or HotSpot VM not loaded
  The -F option can be used when the target process is not responding
  The -F option can be used when the target process is not responding
 
 
  jmap -F -dump:file=/opt/tmp/ap26.dump 1670  
  jmap -F -dump:file=/opt/tmp/ap26.dump 1670  
 
  Attaching to process ID 1670, please wait...
  Attaching to process ID 1670, please wait...
  Debugger attached successfully.
  Debugger attached successfully.

Latest revision as of 23:57, 5 February 2018

External

Internal

Overview

jmap -dump:file=dump.bin <pid>

where <pid> can be obtained with jps.

Capturing Permanent Generation Info

jmap -permstat JBOSS_PID > permstat.out

When JVM is too Busy to Allow Sockets

Use -F:

jbossusr@tcffep4r6ap26 log]$ /opt/jboss/java/jdk1.6.0_29/bin/jmap -dump:file=/opt/tmp/ap26.dump 1670 
1670: Unable to open socket file: target process not responding or HotSpot VM not loaded
The -F option can be used when the target process is not responding

jmap -F -dump:file=/opt/tmp/ap26.dump 1670 

Attaching to process ID 1670, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 20.4-b02
Dumping heap to /opt/tmp/ap26.dump ...