Crash on Linux produces no core or truncated core
 Technote (troubleshooting)
 
Problem(Abstract)
This document outlines what needs to be done to ensure that a full core file is produced on Linux® if WebSphere® Application Server crashes.
 
Resolving the problem

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:
  1. 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.

  2. Ensure that the following ulimit settings are set:

    ulimit -c unlimited
    ulimit -n unlimited
    ulimit -u unlimited

  3. 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.

  4. 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.

  5. If you still do not get a core file after setting these parameters correctly, do the following:
    1. Add the following export statement to the beginning of the startServer.sh script:

      export DISABLE_JAVADUMP=true

    2. Restart the application server.
    3. Issue the kill -11 <PID> command, where <PID> is the process id of the application server.

    4. 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.

    5. 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:
  1. 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.

  2. Enable the Verbose Java Native Interface (JNI) trace.

  3. Restart the application server.

  4. 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

  5. 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.

 
Related information
Exchanging information with IBM Technical Support
Steps to get support for WebSphere Application Server
MustGather: Read first for WebSphere Application Server
Troubleshooting Guide for WebSphere Application Server
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express Hangs/performance degradation Linux 6.0, 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Crash
Operating system(s): Linux
Software version: 6.0
Software edition:
Reference #: 1115658
IBM Group: Software Group
Modified date: Nov 10, 2008