EVALUATION

The problem is that getThreadCpuTime(long[]) is dropping the result on the floor
in the case where there's only one entry in the thread id array.  The fix is to
change the line

getThreadTotalCpuTime0(id);

to

times[0] = getThreadTotalCpuTime0(id);
                                     

EVALUATION

Something is incorrect about the bits being tested. Here is
a snippet of info from ThreadMXBean/ThreadCpuTime.jtr:

#section:script_messages
----------messages:(4/205)----------
JDK under test: (/export/reg/jdk)
java version "1.6.0-internal"
Java(TM) SE Runtime Environment (build 1.6.0-internal-jprtadm_17_Jan_2011_17_57-b00)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)

The JDK1.6.0_25-B01 should be using HSX-20-B07.

The JDK part of the build identifer is right:

    1.6.0-internal-jprtadm_17_Jan_2011_17_57-b00

However, the VM identifer is not right:

     17.0-b17


Here is the same snippet of info from the other .jtr file,
ThreadMXBean/ThreadUserTime.jtr:

#section:script_messages
----------messages:(4/205)----------
JDK under test: (/export/reg/jdk)
java version "1.6.0-internal"
Java(TM) SE Runtime Environment (build 1.6.0-internal-jprtadm_17_Jan_2011_17_57-b00)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode)
                                     

EVALUATION

Please provide URLs for the failures that use HSX-20-B07 bits.
I'm marking this bug as "incomplete" for now.
                                     

SUGGESTED FIX

diff ThreadImpl.java~ ThreadImpl.java
252c252
<                 getThreadTotalCpuTime0(id);
---
>                 times[0] = getThreadTotalCpuTime0(id);
                                     

EVALUATION

This problem is due to a typo in the fix for 6173675.  See Suggested Fix.