Identify and diagnose performance problems in Java™ applications running on HP-UX
Monitor live Java™ applications and analyze profiling data
Capture profiling data with zero preparation when using JDK/JRE 5.0.04 or higher
Run the HPjmeter console on HP-UX, Linux, and Windows® systems
Improve garbage collection performance
HPjmeter features the following functionality:
Automatic problem detection and alerts:
Memory leak detection alerts with leak rate
Thread deadlock detection
Abnormal thread termination detection
Expected out of memory error
Excessive method compilation
System and process CPU utilization thresholds
Heap usage thresholds
Dynamic real-time display of application behavior:
Java heap size
Garbage collection events and percentage time spent in garbage collection
CPU usage per method for hottest methods
Object allocation percentage by method and by object type
Method compilation count in the JVM dynamic compiler
Number of classes loaded by the JVM
Thrown exception statistics
Multi-application, multi-node monitoring from a single console
Drill down into application profile metrics:
Graphic display of profiling data
Call graphs with call count, or with CPU or clock time
Per-thread display of time spent in nine different states
Per-thread or per-process display
Integrated, in-depth garbage collection analysis:
Easy-to-access graphic display of resource utilization by the garbage collector,
including visual presentation of the impact of the garbage collector on application performance
User-configurable graphs for flexibly presenting the collected GC data in alternate relationships
Graphic display of garbage collection behavior that provides insight into thread activity
For best results when using the -Xeprof switch on HP-UX 11.31 on Integrity systems, you should run Java 1.5.0.14 or
later, or 6.0.02 or later, because the thread timing data generated by earlier releases of Java can be inaccurate on 11.31.
How to tell when the thread timing data is off: Because Java can generate an eprof data file with no errors or
other indication of a problem in this situation, you may not know the file is inaccurate until you try to open it with HPjmeter.
Then, HPjmeter will either refuse to load the file, or it will load the file, but display unusual results.
If HPjmeter refuses to load the file, it will display an error message such as Number format error at line NNN. Cannot continue.
If HPjmeter does load the file, you will see unexpected and inaccurate results in the metric displays.
The unexpected results can be seen most easily by examining the Threads Histogram. If you see many threads spending all
their time in an unexpected state, such as "Unknown" or "Lock Contention", then you are experiencing the problem with inaccurate
data. Update your Java installation to one of the versions mentioned above to correct the problem.
Java™ and all Java based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.
Printable version
