AnsweredAssumed Answered

Java OutOfMemory Test

Question asked by CMCN1982 on Oct 17, 2013
Latest reply on Oct 23, 2013 by Awadhesh.D
Recently we had a couple of Java OutOfMemory errors crop up which we were unable to diagnose sufficiently because our heapdump was not configured correctly.

We had:

-XX:-HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\niku\clarity\logs

instead of -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\niku\clarity\logs

so we have changed that in our Sandbox environment for app and bg, restarted services etc.

In order to test if heapdump logs are now being created in the event of an OOM - we thought we would lower the threshold for max heapdump.

Our current config looks like this:

jvmParameters="-Xms2560m -Xmx2560m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\niku\clarity\logs\

if I changed the -Xmx value to something lower, e.g. 200 then this should definitely generate out of memory errors???

When I changed this, and ran admin general upload-config, restarted services nothing seemed to happen. So I rechecked the properties.xml file and now it has a value of 2048, despite me not configuring this?

Has anyone any idea as to how I could carry out my heapdump test better?