WebSphere Crash

Crashes on WebSphere Application Server WebSphere Support Team technical resolutions to crashes, troubleshooting, and known issues articles.

Support Help

Understanding and Diagnosing Crashes

A crash occurs when a process stops or terminates unexpectedly. Generally, crashes may occur because of a Java exception or an OS signal (e.g. SIGSEGV, Signal 11, General Protection Fault (GPF)), and may occur in any part of the native, application, or third-party code.

A crash may also happen due to any kind of memory issues (heap or native), as well as unexpected exceptions (e.g. running out of disk space, etc.). For crashes specifically related to OutOfMemory errors, please see the WebSphere Memory page

Javacores (Also called Javadumps or thread dumps)

System core (Also called coredump or process dump)

System core files must be processed using the jextract tool on the same machine where the file was generated in order to include system libraries. For instructions on using the jextract tool, please see How to process an IBM SDK core dump with Jextract.

If the above dump files were not generated when a WebSphere process ended unexpectedly, this may indicate that the cause was not a ‘crash’ as defined above. There may be several causes for this behavior, which are outlined in the technote: WebSphere Application Server process exits without leaving a footprint in log files or no core dumps.

Technical Notes

How to process an IBM SDK core dump with jextract (Windows, Linux, AIX)

Crash on AIX produces no core or a truncated core

Crash on Linux produces no core or truncated core

WebSphere Application Server process exits without leaving a footprint in log files or no core dumps

MustGathers

MustGather: Crash on Linux

MustGather: Crash on AIX

MustGather: Crash on Windows

“IBM prides itself on delivering world class software support with highly skilled, customer-focused people. ”

Return to 101 home

Contact Support