IBM builds of Java SDK, starting with V1.3.1 SR5 (131-20030618), produce heapdumps automatically when Java heap is exhausted
 Technote (FAQ)
 
Problem
Starting with IBM® Development Kit V1.3.1 SR5 (131-20030618), heapdumps and javacores are automatically produced when the Java™ heap is exhausted.

If you are unaware that the Java heap is repeatedly becoming exhausted, many heapdump files can be generated into the working directory of the Java virtual machine (JVM™).
 
Cause
The default settings of the JVM have been changed, starting with version 1.3.1 SR5 (131-20030618) and later build dates, to help with first failure data capture.

Note: In some cases this might not be desirable, since the heapdumps could fill up the server storage space.

Follow the instructions in this technote to disable the javacores and heapdumps when the Java heap is becoming exhausted.
 
Solution
Disabling HeapDumps for releases of V3.5 and V4.0:
To disable the heap dump, add the following 2 lines to the top of the
startupServer.sh (.bat) file in the $WAS_HOME/bin directory:

export IBM_HEAPDUMP_OUTOFMEMORY=false
export IBM_JAVADUMP_OUTOFMEMORY=false

Disabling HeapDumps for releases of V5.0 and V5.1:
To set the following Environment Entries from the Administrative Console, select:

Servers > Application Servers > server_name> Process Definition > Environment Entries > New

Add the following Name and Value pairs:

Name
Value
IBM_HEAPDUMP_OUTOFMEMORY
false
IBM_JAVADUMP_OUTOFMEMORY
false

Verify changes are saved to the master configuration
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java SDK
Operating system(s): Windows
Software version: 5.x
Software edition:
Reference #: 1158374
IBM Group: Software Group
Modified date: Mar 31, 2004