Express (Distributed operating systems), v8.0 > Troubleshoot and support > Analyzing application server Java system dumps with the IBM Monitoring and Diagnostic Tools for Java - Dump Analyzer
Troubleshoot: common causes of analysis failures
- Truncated or corrupted dump file
- See Technotes with keywords like "truncated core" for detailed instructions but often the cause is that the user settings do not allow enough space for a typical dump file or the drive has insufficient space.
- We are working on making the DTFJ better able to cope with truncated dumps.
- Attempting to analyze an unsupported file format. Currently Dump analyzer can only work on jextracted dump files.
- The tool may take a long time to run
- run time depends on the type of analysis and the size of the dump
- tens of minutes are not unusual run times for large dumps
- JDK 1.4.2 dumps sometimes take longer than JDK 5.0 or 6.0 dumps
- tip: use "HighLevelSummary" or "DefaultDumpReport_Fast" for a quick scan.
- Some information is missing from the report ([null], [unavailable], ...)
- depending on how the dump was produced the information may not be present in the dump at all.
- If you need an analysis module that is not already provided
- let us know
- write one !