不同版本操作系统生成java进程dump的方法及相关解读（Different versions of the operating system to generate java process dump method and related interpretation）.docVIP

不同版本操作系统生成java进程dump的方法及相关解读（Different versions of the operating system to generate java process dump method and related interpretation） Thread Dump is a very useful tool for diagnosing Java application problems, and each Java virtual machine has the ability to produce, in time, the thread-dump that displays the status of all threads at a point. Although each Java virtual machine thread dump print output format is slightly different, but the information contained in Thread dumps out of the thread; thread running, identification and call stack; the call stack contains the full class name, method of execution, if possible, as well as the source code line number. Thread Dump features: Can be used in a variety of operating systems Can be used in various Java application servers Can be used in a production environment without affecting the performance of the system You can locate the problem directly on the applications code line The problems that Thread Dump can diagnose include: Finding memory leaks is a common procedure in which load loads large amounts of data into the cache Found deadlock thread Suns JVM generates the Thread Dump stack information in the following ways: 1, Solaris OS ctrl- \ \ (Control-Backslash) Kill -QUIT pid 2, HP-UX/UNIX/Linux Kill -3 PID PID gets by the following method PS -efHl grepjava| * * * *. 3, Windows Directly to the MSDOS window of the program, press Ctrl-break Some of the Java application server is running on the console, such as Weblogic, in order to facilitate access to information in threaddump, Weblogic starts, it is best to standard output is redirected to a file, use the nohup sh startWebLogic.sh start.log execute kill command, -3 pid, Stack trace will output to start.log. The Dump Thread Tomcat is exported to the command line console or to the catalina.out logs file. In order to reflect dynamic changes in thread status, you need to do thread dump multiple times, each time 10-20s. IBM JVM generates Thread Dump: When memory over