WebLogic Server Support Pattern: Investigating JVM Crashing with No Core Dump (Doc ID 1276688.1)

Last updated on OCTOBER 09, 2024

Applies to:

Purpose

A JVM is an ordinary process like any other, and can sometimes terminate unexpectedly. Java has built-in support for handling exceptions, and JVMs can tolerate run-of-the-mill problems better than most. The very exceptional nature of a JVM crash makes it both interesting and important to determine the root cause, since it can be indicative of a serious problem.

Problem Description

A core dump is usually created when a process crashes. A core file is a memory map of the running process, and it saves the state of the application at the time of its termination. Therefore, it is important evidence (probably the most important) in determining why the JVM crashed.

Sometimes, however, a core dump is not created. This is like a missing body in a murder mystery, and we are forced to fall back on circumstantial evidence (and sometimes reenact the murder) to determine just what killed the JVM. This is the scenario addressed by this document.

Problem Troubleshooting

Please note that not all of the following items need to be done. Some issues can be solved by following only a few of the suggestions.

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.