UCMDB Support Tip: Probe Heap Related Issues
When probe heap issues are encountered, there could be several memory related issues on the probe.
If you come across with such error as: java.lang.OutOfMemory on the probe.
- First step is to check if communication logs for all jobs are disabled. Some jobs generate huge communication logs which can take a great amount of heap space.
- Second step is to make sure that the jobs are scheduled (as opposed to several jobs running at one time). It is recommended not to increase the probe heap to a value higher than 1024 MB. As per http://support.openview.hp.com/selfsolve/document/KM998868
- Third step and the most important in order to avoid memory related issues is to make sure that the swap space on the probe machine is system managed. Under: My Computer -> properties -> Advanced -> Performance Settings -> Advanced -> Change. Check if the space available is system managed size or if it is custom. Custom is where you restrict the virtual memory to not go above a certain size.
Probe is a 32 bit JVM, meaning that the maximum heap size the probe can be set to is 1024 MB. It is not recommended to go beyond 1024 MB. If you set the heap to a value higher than 1024, you might not be left with enough space for stack (you will run into a malloc related error (Native memory allocation (malloc) failed to allocate 65544 bytes for Chunk::new) if it is a stack issue).
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."
Click the KUDOS star on the left to say 'Thanks'