How to generate a jvm Heap dump for troubleshooting issues

Document created by mike_aronson Employee on Jan 10, 2017Last modified by frank_wetzler970218 on Apr 24, 2018
Version 3Show Document
  • View in full screen mode

The Boomi atom, molecule and cloud nodes run on a JVM.


For some issues, you may need to generate a JVM Heap dump for troubleshooting issues.

To generate a heap dump, you should be able to use jmap as described at this link:


It should be distributed with the JDK you have on the server already for the atom, molecule or cloud. 
If you only have the JRE installed, then you will need to download and install the JDK as well.


To use jmap, you would need to determine the process id (PID) of the head node or local atom.


The PID should be a number obtained by looking at either the Windows Task Manager or Windows
Services Manager of your head node or local atom.  Once you have the Windows Task Manager
open, select the Services tab and then find the name of your atom listed.  You should then be
able to see the PID under its column.


Then run this command:

jmap -dump:format=b,file=<some directory that the boomi user has write permission to>/heap.hprof <pid>


On linux you should run the jmap command as the same user as the boomi software runs under. Also the version of the JDK may have to match the version the JVM running as the boomi user is running under. 


Then copy the output from this command and analyze it for performance.


If needed, attach this output to the support case as appropriate.

4 people found this helpful