This page describes how to view and monitor JVM crashes with JVM Crash Guard. When a JVM crash occurs, you need to know as soon as possible. A JVM crash may be a sign of a severe runtime problem in an application and often calls for immediate remediation steps.
When a JVM crash occurs, a corresponding event type is generated in the Controller UI.
To analyze and troubleshoot the crash:
The JVM Crash window also displays information about actions executed as a result of the crash. These are actions that you specify when creating a policy that is triggered by a JVM crash event. See Policies for more information.
The JVM Crash event details include the following information:
In the JVM Crash Details tab, the Crash Reason details field (if available) indicates the root cause of the crash. For example, the field could contain
java.lang.OutOfMemoryError or Segmentation Fault.
To facilitate the discovery and display of the reason for the JVM crash, JVM Crash Guard supports:
Before you can monitor JVM crashes, you must do the following:
/proc/*. This may be the root user or another user with this privilege.
extensions/CrashGuard/conf/crashGuardConfig.ymland open the
Once you have verified the requirements, follow these steps to create a policy for JVM crash events:
Note: If an uninstrumented JVM crash happens within less than a minute of a previous crash, it will not be reported by the Standalone Machine Agent. In some circumstances, the JVM may crash and then be restarted only to crash again within one minute. For this repetitive cycle crash and restart scenario, only the first JVM crash is reported by the agent.