VMWARE Probe stops monitoring intermittently
search cancel

VMWARE Probe stops monitoring intermittently


Article ID: 7403


Updated On:


DX Unified Infrastructure Management (Nimsoft / UIM)


vmware probe stops monitoring intermittently and it works for sometime whenever we restart the probe.

The following are the errors shown in the vmware log files:

Jul 07 10:01:16:303 [attach_socket, vmware] (120) Callback error, Exception in callback for protected void com.nimsoft.nimbus.NimProbeBase.cbStatus(com.nimsoft.nimbus.NimSession,int) throws com.nimsoft.nimbus.NimException: GC overhead limit exceeded: GC overhead limit exceeded 

Jul 07 18:31:58:810 [Data Collector - , vmware] Unexpected fatal error occurred during data collection against DataCollector for  Jul 07 18:31:58:811 [Data Collector - , vmware] java.lang.OutOfMemoryError: Java heap space 

at java.util.Formatter.parse(Unknown Source) 


#### is not responding (reason: Connection and/or inventory update failure)
#### is not responding (reason: Connection and/or inventory update failure)


UIM 8.x or later


Most of the times it would happen because of memory issues with the probe. So allocating proper initial and maximum memory for the probe would resolve the issue.



Increasing the startup parameters for vmware probe would resolve the issue:

1. Open the vmware probe in Raw Configure option. 

2. Go to "Startup" options to increase the initial and max memory settings. 

       java_mem_max = -Xmx4096m 

       java_mem_init = -Xms1024m 

       max_perm_size = -XX:MaxPermSize=512m

3. Change the existing values for options key with below. 

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

4. Cold start (Deactivate and Activate) the probe.

Additional Information

vmware probe release notes