Tuesday, 17 May 2016

Taking Dumps

+++++++++++++++++++++++++++++++++
JVM Thread Dumps
+++++++++++++++++++++++++++++++++
Capture thread dumps 5 times at 30 second intervals against each weblogic server which has the problem.

Example for Hotspot JDK or HP-UX JDK:

JDK_HOME/bin/jstack -l [JVM pid] > srdc_wls_jstack_001.txt
- Wait 30 seconds
JDK_HOME/bin/jstack -l [JVM pid] > srdc_wls_jstack_002.txt
- Wait 30 seconds
JDK_HOME/bin/jstack -l [JVM pid] > srdc_wls_jstack_003.txt
- Wait 30 seconds
JDK_HOME/bin/jstack -l [JVM pid] > srdc_wls_jstack_004.txt
- Wait 30 seconds
JDK_HOME/bin/jstack -l [JVM pid] > srdc_wls_jstack_005.txt

For JRockit use the command:

JDK_HOME/bin/jrcmd [JVM pid] print_threads filename

For AIX JDK use the command

kill -3 JVM_PID

Tip: If the problem is intermittent, capture two sets of thread dumps; one set at time when the server is working fine, another set when the server is reproducing the problem.

jstack pid > threads.out
---------------------------------------------------------------------------------------------------------


+++++++++++++++++++++++++++++++++
JVM Heap Dumps
+++++++++++++++++++++++++++++++++

For JDK

JDK_HOME/bin/jmap pid >heap.out

JRockit

JDK_HOME/bin/jrcmd [JVM pid] print_objects filename

------------------------------------------------------------

For Console

use Jconsole







No comments:

Post a Comment