AIX系统dump文件分析工具
To invoke?<dumpfile> [<outputfile]On z/OS?, you can copy the dump to an HFS file and supply that as input to?> jextract USER1.JVM.TDUMP.SSHD6.D070430.T092211Loading dump file...Read memory image from USER1.JVM.TDUMP.SSHD6.D070430.T092211VM set to 10BA5028Dumping JExtract file to USER1.JVM.TDUMP.SSHD6.D070430.T092211.xml<!-- extracting gpf state -->...Finished writing JExtract file in 5308msCreating zip file: USER1.JVM.TDUMP.SSHD6.D070430.T092211.zipAdding "USER1.JVM.TDUMP.SSHD6.D070430.T092211" to zipAdding "USER1.JVM.TDUMP.SSHD6.D070430.T092211.xml" to zipAdding "/u/build/sdk/jre/lib/J9TraceFormat.dat" to zipjextract complete.This produces a compressed (.zip) file in the current HFS directory.
The?-nozip
By default, output is written to a file called?<dumpfile>.zip in the current directory. This file is a compressed file that contains:
Typically, you would send the compressed file to IBM? for problem diagnosis.?Submitting data with a problem report?tells you how to do that.
To analyze the dump locally, extract the compressed file using?unzip -d dir?<file>?or?jar xvf?<file>. You are also advised to run?If you run?You can still use the dump viewer on the dump, but it will be limited in the detail that it can show.
The contents of the compressed file produced and the contents of the XML are subject to change, so you are advised not to design tools based on them.
?
?
The?-d<dumpfile>
Typical usage is?jdmpview?<dumpfile>. The?dumpfile.xml.
After?Ready.... When you see this message, you can start calling commands on?You can significantly improve the performance of?-Xmx?option to increase the maximum heap available to-J. For more information about using?-Xmx, see?Command-line options.The xml file produced by?It might be useful to convert the xml file to EBCDIC for viewing on z/OS, but make sure you keep the ASCII version for use in?
The IBM? Monitoring and Diagnostic Tools for Java? - Dump Analyzer (referred to hereafter as the Dump Analyzer) is intended to perform automated analysis of dump files produced by the IBM Java VM. Starting with the name of the dump to be analyzed the analysis will attempt to localise the problem and if successful will produce a diagnosis of the error together with sufficient information to fix it or suggestions on how to continue the analysis using other tools (e.g. MDD4J to diagnose out of memory situations). If localization fails then the tool will default to producing summary information from the dump intended to aid further diagnosis.
The Java language has come to be predominant in software development, and thus the reliability of the Java Virtual Machine (VM) has become a very important issue. The VM is typically a reliable piece of software, but of course failures do occur during execution for a variety of reasons. A small number of these problems are due to errors in the VM itself; however, in the majority of cases, they are due to errors or misconfigurations in the software stack above the VM (in WebSphere? Application Server, for instance) or in the application itself.
The software stack for a typical projects has increased in complexity as information technology has matured, which has led to increasing difficulties for developers trying to determination the causes of problems. In such a complex environment, you may be faced with an overwhelming excess of information with which to diagnose the fault. In a production environment there may well be many gigabytes of heap, hundreds of threads, thousands of classloaders, tens of thousands of classes, and a huge number of objects.
The Dump Analyzer is an extensible framework that seeks to solve this problem for the IBM Java SDK's. It uses analyzers to interrogate a formatted system dump (each analyzer asking the dump a specific question) and links them together with a script to produce a concise report of the analysis. Typical problems analyzed might be the following.
The aim is to diagnose the correct category of problem and either provide a complete diagnosis of the problem or give some information designed to aid diagnosis together with a recommended next course of action.
出处：http://publib.boulder.ibm.com/infocenter/javasdk/v5r0/index.jsphttp://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.java.diagnostics.dbda.isav4.doc/docs/overview.html?
