delays in alarms from vmware probe: java.lang.OutOfMemoryError: GC overhead limit exceeded
search cancel

delays in alarms from vmware probe: java.lang.OutOfMemoryError: GC overhead limit exceeded

book

Article ID: 386224

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

We have noticed that alarms from the vmware probe stopped being sent for a period of time. So some alarms arrived with a considerable delay. 

The following message was observed in the vmware.log: 

java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded 

Environment

  • DX UIM 23.4.*
  • vmware probe 7.x

 

Cause

The error message java.lang.OutOfMemoryError: GC overhead limit exceeded strongly suggests that the Java process handling the VMware probe is running out of memory, specifically related to garbage collection (GC). The "GC overhead limit exceeded" message indicates that the JVM (Java Virtual Machine) is spending too much time on garbage collection without being able to free up enough memory, which is typically a sign of insufficient heap space allocated for the process.

Resolution

ACTIONS TO TAKE

  •  Increase JVM Heap Size for the VMware Probe

    The default memory allocation may be insufficient for the probe's needs, especially if you're dealing with a large environment or a high volume of data. You can increase the heap size allocated to the VMware probe by adjusting the JVM parameters.

    Example. If Current configuration is: 

        options = -Xms2048m -Xmx4096m -Duser.language=en -Duser.country=US

    Change it to: 

       options = -Xms3072m -Xmx6194m -Duser.language=en -Duser.country=US

  • And monitor this issue for some time.