Collecting heap dump in Gateway

Module Development
1

I have a customer that is experiencing out-of-memory errors in the Gateway - causes Gateway re-starts. I’d like to collect information for analysis - tried changing the ignition.conf file. My attempt shown below was only a guess and didn’t work. What should it have been?

NOTE: Configuration below has been edited/corrected per Kevin’s suggestions …

. . .
# Java Additional Parameters
wrapper.java.additional.1=-XX:PermSize=64m
wrapper.java.additional.2=-XX:MaxPermSize=128m
wrapper.java.additional.3=-XX:+UseConcMarkSweepGC
wrapper.java.additional.4=-XX:+CMSClassUnloadingEnabled
wrapper.java.additional.5=-XX:+CMSPermGenSweepingEnabled
wrapper.java.additional.6=-Ddata.dir=data
wrapper.java.additional.7=-Dorg.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false
wrapper.java.additional.8=-Xdebug
wrapper.java.additional.9=-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000
wrapper.java.additional.10=-XX:+HeapDumpOnOutOfMemoryError
wrapper.java.additional.11=-XX:HeapDumpPath=/Users/me/Datafiles
. . .

Thanks,
— chuck

2

I think those parameters are just supposed to be ‘10’ and ‘11’, not ‘a’ and ‘b’.

3

Unfortunately the gateway won’t start if I add options as proposed above - even with the re-numbering, Bottom line is I still don’t know how to get an out-of-memory dump friom the Gateway,

– chuck

4

This JVM options documentation says the option is “-XX:-HeapDumpOnOutOfMemoryError”, and I see you’re using a ‘+’ instead.

I’m able to start a gateway successfully using the correct option.

5

Thanks Kevin, got it correctly configured (though I haven’t seen a dump yet). I edited the original post to show it corrected.
— chuck