Isolating the high JVM garbage collection problems

Use Z Automation Web Console to isolate the garbage collection problem to deep dig into the cause and the solution.

About this task

The Problem Isolation - Garbage Collection dashboard provides detailed garbage collection information for the monitored JVM to help you analyze the root cause.

Procedure

Complete the following steps to isolate the JVM with Java™ heap and garbage collection problems.

  1. Check the data in chart Heap Occupancy Over Time.
    You can see the heap occupancy keeps consistently high.
    A screen capture of chart heap occupancy over time
  2. In the Suggested Actions widget, click the drop down icon and select Maximize to maximize the widget.
    maximize the widget
  3. Review the problem description and suggested actions to identify the root cause and solution.
    From the Suggested Actions, one option is to increase the maximum heap size.
  4. Click the drop down icon and select Restore to restore the widget to the original size.
    A screen capture of clicking 'restore'
  5. Review the current Java heap size in the Selected GC Details widget.
    The maximum allowable heap size for the JVM is set to 156 MB.
    A screen capture of the selected GC details

Results

In this scenario, the maximum Java heap size is set too low for the amount of concurrent work being executed. Increasing the maximum heap size will enable the JVM to use more memory and reduce the rate of garbage collections and resulting pauses.

What to do next

Congratulations! You've successfully identified a JVM with insufficient Java heap and investigated the problem for the follow-up action!