This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.

Skip to end of metadata
Go to start of metadata


When a JVM crash occurs,you need to be notified as soon as possible.  Learning of a JVM crash is very critical because it maybe a sign of a severe runtime problem in an application.  Furthermore, you may want to to take remediation steps once you are aware that a crash event has occurred.  JVM Crash is a new event type, implemented as part of JVM Crash Guard, that you can activate to provide you with the critical information you need to expeditiously handle JVM crashes.

The following image shows the Events window where notification of two JVM Crash events detected is displayed. 

Double-clicking the JVM Crash event on the Events window displays more information to assist you in troubleshooting the underlying reason for the JVM crash.  

On the Summary page you can download any logs associated with the JVM Crash event.

The JVM Crash window also displays information about actions executed as a result of the crash. These are actions that you specify when creating the policy that is triggered by a JVM crash event.

The JVM Crash event captures the following information: timestamp, crash reason, host name, IP address, process ID, application name, node name, and tier name and displays them on the details page. 

In the Crash Reason details field of the JVM Crash Details tab, the JVM Crash details indicate the root cause of the crash if available; for example, a java.lang.OutOfMemoryError, Segmentation Fault, etc... To facilitate the discovery and display of the reason for the JVM crash, JVM Crash Guard provides full support for:

  • Hotspot JVM error log analysis
  • IBM JVM System Dump log analysis
  • Jrockit JVM error log analysis

To Start Monitoring for JVM Crashes


JVM Crash Guard is a policy trigger that works with the Standalone Machine Agent to fire an AppDynamics policy when a JVM Crash event occurs. You must therefore have a Machine Agent installed on the system which you want to monitor for JVM crashes. On Windows, the Machine Agent must run in Administrator root mode. On Linux, JVM Crash Guard requires that the Machine Agent user be able to read all the processes in /proc/*. This may be the ‘root’ user or another user with this privilege.
  1. From the left-hand navigation menu, click Alert & Respond ->Policies and then click Create a Policy.
    Navigate to the Policies tab and then click Create a Policy.
    The Create Policy dialog appears.
  2. In the Other Events section, expand the Server Crashes option and click JVM Crash.  
    The JVM Crash event then becomes a trigger to fire a policy. 
  3. Proceed as usual to create the Policy. For more information on creating Policies, see Policies

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.


  • No labels