![](/images/backgrounds/286181/hp-hp-ux-java-software-users-manual-156066110x1.png)
The window shows events in a hierarchical tree.
•Select the View→Show Packages menu item to alternatively hide or show the Java package names to shorten the lines in the display.
•Select the View→Show Stacktraces menu item to alternatively expand or collapse the thrown stack traces of all the exception nodes, or click on a specific node to expand or collapse its thrown stack trace only.
The results are cumulative over the life time of the session.
See also:
•Identifying Abnormal Thread Termination (page 44)
Excessive Compilation AlertBy default, HPjmeter detects when one method (or more) is repeatedly compiled.
See also: Identifying Excessive Method Compilation (page 46) .
Expected Out Of Memory Error AlertHPjmeter detects memory leaks automatically and reports an alert before a crash occurs. By default, this alert activates when memory use increases by a rate of 10 MB/hr.
The heuristic algorithms for alert triggers are tuned for
To confirm the leak, monitor the application for one hour or longer; then review the Garbage Collections metrics.
See also:
•Garbage Collections (page 123)
•Confirming Java Memory Leaks (page 43)
•How Memory Leak Detection Works (page 189)
GC Duration NotificationSet this threshold when you suspect that the duration of garbage collections exceeds or is significantly less than what is reasonable for the application heap size.
The Alert Controller displays this alert threshold differently depending on the Java version run with the application.
Table
Java Version | Metric Name | Default Alert Threshold |
HP 1.4.2.02 or later 1.4.x versions | GC Duration | > 2000 milliseconds (2 seconds) |
HP 1.5.0.12 or 6.0.01 or later | GC Duration (Major) | > 30 seconds |
HP 1.5.0.12 or 6.0.01 or later | GC Duration (Minor) | > 2000 milliseconds |
|
|
|
See also:
110 Using the Console