When it comes to locating the system, we often need to understand and analyze the runtime state of the JVM. What should be the starting point? The answer is to start with the data. The data here include:
GC logs, exception stacks, thread snapshots (threaddump), heap dump snapshots (heapdump), and so on. The JDK is built with a wealth of virtual machine monitoring and analysis tools to use.
Can make our trouble shooting more with less.
Oracle Hotspot JDK Monitoring Analysis tool
Name |
Role |
JPs |
The JVM process Status tool, which displays all the hotspot virtual machine processes running in the system |
Jinfo |
Configuration info for Java, displaying the virtual machine's config information |
Jmap |
Memory map for Java, generating a ram dump snapshot of a virtual machine (threaddump) |
Jstack |
Stack trace for Java, displaying a thread snapshot of a virtual machine |
Jstat |
JVM Statistics monitoring tool to display runtime state data for a hotspot virtual machine |
Reference articles
Trouble Shooting Guide for Javase 6 with HotSpot VMS:
Http://www.oracle.com/technetwork/articles/javase/monitoring-141801.html
"Monitoring and managing Java SE 6 Platform Applications"
Http://www.oracle.com/technetwork/java/javase/tsg-vm-149989.pdf
Monitoring and troubleshooting tools in the JDK-01