How Webshpere closes dump file generation

The root cause of the heapdump is your Java stack overflow. Solutions:
1. Increase the heap space
2. Check for memory leaks in the application
3. Please see the following explanation:

Why is the IBM JDK of WebSphere Application Server upgraded to V1.3.1 After SR5, heapdumps and javacores are always automatically generated. How to avoid it?

Product : WebSphere Application Server (hereinafter referred to as WAS)
Version: 4.0.x, 5.0.x, 5.1.x
Platform: AIX, Windows, Linux JDK always automatically generates heapdumps and javacores after upgrading to V1.3.1 SR5 : In order to assist in capturing error continuation information at the first time, starting from IBM JDK V1.3.1 SR5 (131-20030618), when the Java heap space is exhausted When the system will automatically generate heapdumps and javacores. If you want to not automatically generate heapdumps and javacores when Java runs out of space, please follow the steps below: For WAS 4.0.x: 1. Find the <WAS_HOME>/bin/startupServer.sh (.bat) file, where <WAS_HOME> indicates the WAS installation directory 2. Open the file with a text editor and add the following 2 lines at the top of the file: export IBM_HEAPDUMP_OUTOFMEMORY=false











export IBM_JAVADUMP_OUTOFMEMORY=false
3. Save and close the file, restart WAS

For WAS 5.0.x or 5.1.x:
1. Open the admin console and select: Servers > Application Servers > Server Name to Change > Process Definition > Environment Entries
2. Create the following 2 entries:
Name Value
IBM_HEAPDUMP_OUTOFMEMORY false
IBM_JAVADUMP_OUTOFMEMORY false
3. Save the configuration changes and restart WAS