If you have already contacted support, continue to the following
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Crash-specific MustGather information
Follow these steps to ensure that a core file is produced on Linux
when the Java™ Virtual Machine (JVM) crashes:
- Add the following export statement in the file
startServer.sh:
export
JAVA_DUMP_OPTS="ONERROR(JAVADUMP,SYSDUMP),
ONEXCEPTION(JAVADUMP,SYSDUMP),ONDUMP(JAVADUMP)" |
|
Note: The preceding two lines are broken due to
length. The two lines should be joined and added as a single line in the
script. |
|
- Ensure that the following ulimit settings are set:
ulimit -c unlimited
ulimit -n unlimited
ulimit -u unlimited |
|
 |
 |
- Ensure that the WebSphere Application Server process can write to the
directory to which the core file will be written. The default is the
working directory. Also ensure there is enough free file system space in
the directory for the core file.
- To test to see if you can get a core file, issue the kill -11
<PID> command, where <PID> is the process id of the
application server.
- If you still do not get a core file after setting these parameters
correctly, do the following:
- Add the following export statement to the beginning of the
startServer.sh script:
export DISABLE_JAVADUMP=true |
|
- Restart the application server.
- Issue the kill -11 <PID> command, where
<PID> is the process id of the application server.
- If you cannot get a core file from the test, determine if you can
obtain a core file from any process on the machine by issuing a kill
-11 <PID> against the PID of another running process.
- If you can get a core file from the test, wait for a crash to occur
during an error condition.
Note: You can also search for core files in the following directories:
- install_root/bin
- Configured Application Server working
directory
- /tmp
If you cannot find a core file in any of these directories, search your
entire machine for core* files.
What to do if the crashing JVM still does not produce a core after a
crash:
- Collect the following diagnostic information:
- All logs from the WebSphere Application Server that is
crashing.
- /usr/var/messages
- Description of the application, including use of back-end
systsms and native code.
- Enable
the Verbose Java Native Interface (JNI) trace.
- Restart the application server.
- After the next crash of the application server, collect the following
diagnostic information:
- All logs from the application server that is
crashing.
- /usr/var/messages
- Follow instructions to send diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to crash, search the WebSphere
Application Server support site.
|