Menu
Currently I have a deployed executable jar file that creates large (7+ Gb) minidump files when it crashes. I would like to have a text representation of what caused the crash, not a binary file of the JVM state. I've tried using the information found in this CodeRanch post and the documentation that I've found in the Java documentation doesn't seem to help.
I also referenced this question but there's no definitive answer.
Is there a typical way this is done that I'm not aware of?
315
To disable generation of MDMP files: Go to InstallerVars file. Change the option: - XXdumpsize to 'none', as per the below screenshot.
The mdmp files are the compressed dumps that are sent to microsoft. As these are just files being used for debugging, you can delete them all safely. If your userdumps folder continues to gain these files, then your system is having problems. Any application that crashes will leave these dump files.
Can you configure where and if . mdmp dump files are created? yes depends on operating system.
The Windows minidump file is found in the "minidump" subfolder of the Windows system folder (e.g., "C:\Windows\minidump") and looks somewhat similar to this: Mini030915-01. dmp.
I found a command line option that seems to do what I want. Launching the jar with
java -XX:-CreateMinidumpOnCrash -jar myJar.jar
Seems to do the trick and will generate error logs that are very small compared to the minidumps.
197
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With