HPjmeter 4.3 Release Notes and Installation Guide

Table 1 Defect Fixes in HPjmeter 4.3 Release (continued)
Behavior in 4.2 or Older VersionsNew Behavior in 4.3Defect Tracking Number
30s, GC Duration (Minor) >= 2000ms”.
Also, the same time units (seconds for Major
Duration (Minor) >= 20.0”. In this case,
the 30 is measured in seconds, the 20 is
and milliseconds for Minor) are now used measured in 100s of milliseconds, and the
when setting the alert thresholds in the Alert
Controller window.
visualizers graph used milliseconds on the
Y axis. This mixing of units could be
confusing. Also, when setting the alert
threshold for Major GC’s, the time units
were measured in seconds, while for Minor
GC’s, the time units were 100s of
milliseconds.
When the Edit -> Standard Preferences ->
Export Preferences to File option is selected,
The HPjmeter console was modified to only
export the user preferences that are related
to HPjmeter.
QXCR1001115453
HPjmeter was exporting all user
preferences, not just those that were
specific to HPjmeter.
While reading an ascii format heap dump
file, HPjmeter could throw an
HPjmeter was modified to handle the ascii
heap dumps that do not have certain thread
information.
QXCR1001177717
ArrayIndexOutOfBoundsException, if the
file was missing certain thread information.
HPjmeter 4.2 will occasionally fail to
instrument a class because it cannot locate
An improved algorithm allows HPjmeter to
obtain the desired classloader instance for
QXCR1001207970
the desired classloader. This did not leadmore classes while performing bytecode
to any errors, but there would be less metric
data related to the class.
instrumentation. This allows HPjmeter to
perform instrumentation on more classes,
resulting in improved metric data.
The Method Compilation Frequency
visualizer does not contain a label on the
Y axis.
Improved Y axis label specification for many
of the visualizers such as Method
Compilation Frequency.
QXCR1001220078
Due to an issue with the dynamic attach
feature when loading the HPjmeter JVM
This problem has been fixed, improving JVM
agent metrics for more classes within the
standard Java packages.
QXCR1001230409
agent, a few classes related to array leaks
and collection leaks in the standard Java
packages were not being instrumented.
A problem existed where the first garbage
collection reported would not reappear in
This problem has been fixed. The first
garbage collection reported is shown in the
QXCR1001247440
the visualizer if a request to “Refresh Data”Heap Usage After GC visualizer when a
“Refresh Data” button is selected. was made using the Heap Usage After GC
visualizer to view the –Xloggc garbage
collection data.
Defect Fixes 9