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 call calls for immediate remediation steps.
This topic describes how to use AppDynamics JVM Crash Guard, which you can use to monitor and remediate JVM crashes.Viewing JVM Crash
View JVM Crash Information
When a JVM crash occurs, a corresponding event type is generated in AppDynamicsthe 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 Crash Reason details field of the the JVM Crash Details tab, the JVM Crash details indicate Reason details field (if available) indicates the root cause of the crash if available. For example, a the field could contain
To facilitate the discovery and display of the reason for the JVM crash, JVM Crash Guard supports:
Enable Monitoring for JVM Crashes
Before you can monitor JVM crashes, you must do the following:
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 then , 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.