JDK-7013682 : two test checking cpuTime filed java/lang/management/ThreadMXBean
  • Type: Bug
  • Component: core-svc
  • Sub-Component: java.lang.management
  • Affected Version: 6u25
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,linux
  • CPU: generic,x86
  • Submitted: 2011-01-20
  • Updated: 2011-12-29
  • Resolved: 2011-04-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u25 b01Fixed 7Fixed
Related Reports
Duplicate :  
Relates :  
Description
see comments

Comments
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);
27-01-2011

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

EVALUATION This problem is due to a typo in the fix for 6173675. See Suggested Fix.
21-01-2011

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

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)
21-01-2011