Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


On this page:

Related pages:

When a JVM crash occurs, you need to be notified as soon as possible. Knowing about a JVM crash is critical because it may be a sign of a severe runtime problem in an application. Furthermore, you may want to take remediation steps when a crash event has occurred. 

JVM Crash is an event type implemented as part of JVM Crash Guard that can provide you with critical information for handling JVM crashes.

The following image shows the Events window with two JVM Crash events: 

Double-click the JVM Crash event on the Events window to see more information on troubleshooting the cause of the JVM crash.  

To perform root-cause analysis and troubleshooting:

  • In the Events window, double-click the JVM Crash of interest.  
  • Examine any logs associated with the JVM Crash event. (The local log folder is determined by the type of JVM and how it is configured. For more information, refer to the documentation for the specific JVM.)

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 or Segmentation Fault. 

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

Start Monitoring for JVM Crashes

JVM Crash Guard works with the Standalone Machine Agent to trigger an AppDynamics policy when a JVM Crash event occurs. You must therefore have a Machine Agent installed and enabled on the machine that 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.

Once you have verified the requirements, follow these steps to create a policy for JVM crash events:

  1. From the left-hand navigation menu, click Alert & Respond > Policies and then click Create a Policy
  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. 

Watch the Video

For full-screen viewing, click Standalone Machine Agent - Overview of JVM Crash Guard


  • No labels