HPjmeter 4.2 Release Notes and Installation Guide

2 New in This Version
Various enhancements and defect fixes are included in this release.
New Features and Enhancements
HPjmeter 4.2 provides the following major enhancement:
• When viewing an hprof file, you can use the enhanced Reference Sub-Trees by Size metric
viewer to display object and primitive values for any selected node object in the tree. These
values are displayed in a table on the right side of the viewer. This table has two tabs:
— The Attributes tab shows the names and values of the non-static fields in the node object.
— The Statics tab shows the names and values of the static fields in the node object.
See the HPjmeter 4.2 User's Guide for information on these enhancements.
Defect Fixes
Defect fixes provided in HPjmeter 4.2 result in improved data accuracy and reduced memory
usage.
Defect fixes include those in the following table:
Table 2-1 Defect Fixes in HPjmeter 4.2 Release
Behavior in 4.1 or Older VersionsNew Behavior in 4.2Defect Tracking Number
swverify would issue error messages
when verifying the HPjmeter installation
on HP-UX.
These error messages no longer appear.QXCR1001152071
HPjmeter could display misleading
profiling data in thread scope. A thread
Misleading profiling data is no longer
displayed in thread scope. If a thread does
QCXR1001085548
might not have data for every metric. Ifnot have any data to display for a given
metric, the display now shows “No data.” the user is viewing a metric and switches
to a thread that has no data for that metric,
HPjmeter would continue to display the
data from the previous thread.
HPjmeter JVM agent could crash 64-bit
JVM on PA-RISC.
This bug has been corrected so that the JVM
does not crash in this situation.
QXCR1001089137
HPjmeter could display incorrect data for
the Exclusive Class Times display.
Only correct data is displayed for the
Exclusive Class Times display.
QXCR1001104804
Under unusual circumstances, several
node agent threads could deadlock while
trying to acquire a resource.
This deadlock no longer occurs.QXCR1001114827
If an error occurred while decompressing
a compressed input file, HPjmeter would
delete the input file.
HPjmeter no longer deletes the input file in
this case.
QXCR1001115844
The HPjmeter console could throw an
exception while using the Array Leak
viewer.
The HPjmeter console does not throw an
exception while using the Array Leak
viewer.
QXCR1001121281
The JVM would throw VerifyError when
a program used CopyOnWriteArraySet
with the memory leak metric.
The JVM no longer throws VerifyError in
this situation.
QXCR1001135127
Suppose a Java application was executed
with the HPjmeter agent, and it created a
A Java application that uses
ObjectOutputStream/ObjectInputStream
QXCR1001110175
file using ObjectOutputStream. If that filefor serialization works as expected with the
HPjmeter agent. was read back using ObjectInputStream
by a Java application that was not using
the HPjmeter agent, then the application
8 New in This Version