On this page:

Related pages:

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 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 Information

When a JVM crash occurs, a corresponding event type is generated in AppDynamics. The following screenshot shows JVM Crash events in the AppDynamics UI: 

  

To analyze and troubleshoot the crash:

  1. In the Events window, double-click the JVM Crash of interest.  
  2. 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. See Policies for more information.

The JVM Crash event details include the following information:

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 supports:

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. Additionally:

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

<style type="text/css">.vidyard_player{width: 600px; }.vidyard_player > span{max-width: 600px !important; max-height: 360px!important;margin-left:0!important;}.innerContainer{position: relative; display: block; width: 100% !important; height: 0; }</style><script type="text/javascript" id="vidyard_embed_code_CQsf7mmnXSc7hufoQ8VPHT" src="//play.vidyard.com/CQsf7mmnXSc7hufoQ8VPHT.js?v=3.1.1&type=inline&second=0"></script>

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