I have java application that is crashing while in production. It doesn't do so in dev/QA. The jvm is creating a .mdmp file and a text file. How do I analyze the binary dump file? I googled but had no luck. We are using bea jrockit jvm 1.5 R27.
There are many different programs you can use to open MDMP files. If the file doesn’t open when you double-click it, you may not have one of these programs on your computer. Try installing the most common program associated with MDMP files, WinXP Trouble Report. If this program doesn't work, move to Step 3. Step 3: Figure Out the File Type. The file type can give you a clue as to which programs can open your MDMP file. How to read MongoDB.mdmp files. If the dump was saved with heap information, the dump file contains a snapshot of what was in the app's memory at that point in time. Opening a dump file with a heap in Visual Studio is like stopping at a breakpoint in a debug session. Although you cannot continue execution, you can examine the stacks, threads.
2 Answers
The .mdmp
file is a Windows MiniDump file that you can only read with a debugger (like WinDbg). Typically you need the sources of the crashed application to really get some information out of the dump. So in your case you can't do much but contacting JRockit support.
Here a link to the Orace JRockit information about JVM crahes.
If you want to look at the heap of the crashed process you can use a tool that ships with the JDK called jmap
to extract a HPROF file and then load this into a memory analyser. Note also that some memory analyzers can load core dumps and Windows minidumps directly.
Related issue and the jmap docs
If you want to see the state of the threads then you can use a tool called jstack
to print stack traces for every thread at the point the dump was created. jstack docs.
Not the answer you're looking for? Browse other questions tagged javadumpjrockit or ask your own question.
I have java application that is crashing while in production. It doesn't do so in dev/QA. The jvm is creating a .mdmp file and a text file. How do I analyze the binary dump file? I googled but had no luck. We are using bea jrockit jvm 1.5 R27.
![How to open dmp files in windows 10 How to open dmp files in windows 10](http://windowscoding.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/blake/WinDbg6.11.0001.404AMD64_5F00_thumb_5F00_66EF0C75.png)
2 Answers
The .mdmp
file is a Windows MiniDump file that you can only read with a debugger (like WinDbg). Typically you need the sources of the crashed application to really get some information out of the dump. So in your case you can't do much but contacting JRockit support.
Here a link to the Orace JRockit information about JVM crahes.
If you want to look at the heap of the crashed process you can use a tool that ships with the JDK called jmap
to extract a HPROF file and then load this into a memory analyser. Note also that some memory analyzers can load core dumps and Windows minidumps directly.
Related issue and the jmap docs
If you want to see the state of the threads then you can use a tool called jstack
to print stack traces for every thread at the point the dump was created. jstack docs.