Preetham R Enjamuri

• Jan 17th, 2012

 

Get the pid of the JVM (either from logs directory) or do a ps-ef |grep
then by using the pid
kill -3
Heap dumps location generally in the logs folder.
or you can change the location by getting into the admin console.

Ritam

• May 5th, 2013

 

To generate a heap dump we need to login to dmgr level bin directory and run the below

Code
./wsadmin.sh<----after that wsadmin prompt will come


 


wsadmin>set jvm[$AdminControl CompleteObjectNames 


 


type=jvm,process=server1,*]<---server1 will be that server for which you are taking dumps


 


wsadmin>$AdminControl.invoke $jvm generateheapdumps


 


 


Default location:temp

pardeep131085

 Profile Answers by pardeep131085 Questions by pardeep131085

• Aug 21st, 2013

 

There are several method to take heap dump, see the following methods

HeapDumpOnCtrlBreak
Set this option when starting JVM.It will create heap dump every time ctrl+break (kill -3) signal is sent to JVM. HeapDumpPath is used to set location of heap dumps.
HeapDumpOnOutOfMemoryError
This JVM option will create heap dump every time when your application throws an OutOfMemoryError
Jmap
Jmap is a tool that comes with JDK installation. To use it we need a PID of our java process.
For instance, jmap -dump:file=C:heapdumpsdump.bin 1212
HotSpotDiagnosticMXBean
This option is available in Java 1.6+ and uses sun.management.ManagementFactory.

Once we get the heap dump, we can analyse a tool like VisualVM (also included in JDK installation)to actually try and find the leak.
Another tool is jhat. Command to analyze heap dump

Reference : http://java-latte.blogspot.in/2013/08/stack-and-heap-in-java.html