Red Hat Bugzilla – Bug 534450
should we enable heap-dump-on-error in both agent and server?
Last modified: 2014-05-02 16:38:46 EDT
Should we start the server and agent with the following VM parameters: -XX:+HeapDumpOnOutOfMemoryError writes heap dump on OutOfMemoryError (recommended) -XX:+HeapDumpOnCtrlBreak writes heap dump together with thread dump on CTRL+BREAK See: http://wiki.eclipse.org/index.php/MemoryAnalyzer These are only valid for SUN HotSpot VMs, but since it covers the majority of people's VMs, it might be useful to have this turned on by default in our launcher scripts/configuration.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1244
Per triage, we are going to doc this for now, provide information on how to enable if necessary. Deon, please talk with developer to determine the best place to put this, and how to word it.
I'm changing the component to Documentation for the moment, so it shows up in my queue and I don't forget about it.
Here is the reference we can include in our documentation http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html#DebuggingOptions We would suggest to people, if they are seeing the server crash due to OutOfMemoryError issues, to restart with the following VM options: -XX:-HeapDumpOnOutOfMemoryError If the user wants the heap dump file to be dropped in a particular location, they can additionally specify: -XX:HeapDumpPath=./java_pid<pid>.hprof