Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 6683213
Votes 0
Synopsis CounterMonitor's derived Gauge badly initialized
Category jmx:classes
Reported Against
Release Fixed 6u12(b02), 7(b41) (Bug ID:2169536) , 6-open(b14) (Bug ID:2169540)
State 11-Closed, Verified, bug
Priority: 3-Medium
Related Bugs 6674849 , 6683341 , 6771136
Submit Date 02-APR-2008
Description
In the JMX 1.4 Specification, PDF document, paragraph 9.3, we read:
"The derived gauge value (V[t]) for the counter difference is calculated at time t
using the following algorithm, where GP is the granularity period:
    While t is less than StartDate+2GP, V[t] = (Integer)0"

The issue is that the derived Gauge value is null when is less than StartDate+2GP with JDK 6.
Because of that, a CounterNotification is potentially not emitted as it should.
This is a regression compared to JDK 5.
Attached output of a test run once over JDK 6 U5 b13 and once over JDK 5 U15 b08.
That test uses a threshold set to 2, a modulus set to 7, uses difference mode. We set the observed  customer  to 0, 1, 2, 7. Granularity period is 500 ms and setAttribute calls are done every second.
Posted Date : 2008-04-02 09:19:31.0

The correct set of JCK tests hit by this defect is MonitorTest tests numbered 4, 5, 6, 13 and 20.
The tests numbered 1, 3, 32 and 33 do not use the difference mode then they've no chance to be hit by a wrong derived gauge computation.
Posted Date : 2008-09-10 16:15:11.0
Work Around
N/A
Evaluation
The spec is right and the implementation needs to be changed to follow the spec.
Posted Date : 2008-05-21 13:13:38.0
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang