The WebSphere Application Server (WAS) JVM checks each of the following locations for existence and write-permission, and stores the Javadump, Heapdump, or System Coredump, in the first one available:
- The location specified by the IBM_JAVACOREDIR, IBM_HEAPDUMPDIR and IBM_COREDIR environment variables if set (_CEE_DMPTARG on z/OS).
- The current working directory of the JVM processes or $WAS_HOME/profiles/<ProfileName> dir.
- The location specified by the TMPDIR environment variable, if set.
- The /tmp directory or, on Microsoft Windows only, the location specified by the TEMP environment variable, if set.
- Windows only: If the Javadump cannot be stored in any of the above, it is put to STDERR.
Environment Variables to be set for Dump Directory Location:
To set these variables for each individual server in the Integrated Solutions Console
- Open the Administrative Console.
- Select Servers > (Expand Server Types) > WebSphere application servers > server_name > (Expand Java and Process Management) > Process Definition > Environment Entries > New.
- Add entries to the Name/Value pairs (from above Environment Variables).
- Click OK.
- Save changes to the master configuration, make sure node is synchronized, and restart the Application Server in the console.
To set these environment variables in a Script
- Edit ..<WASHome>/profiles/profile name/bin/setupCmdLine.sh and Add the lines below:
Edit ..<WASHome>/profiles/profile name/bin/startServer.sh and Add the lines below:
- Then Stop all applicable WAS servers, including the DMgr and nodeagent, and re-Start the JVMs from the command line.
Note: you must have enough free disk space for the Dump file to be written correctly to the file system, so directory space or ulimits need to be set accordingly.
For example: on AIX, Linux, or Unix, you can set ulimits for Core and File
ulimit -c unlimited
ulimit -f unlimited
If you have limited resources, then you can set whatever values work best for your environment given available disk space and installed physical memory.