JDK-6235077 : javax.management.timer.Timer doc inconsistent about what happens for Date in the past
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2005-03-02
  • Updated: 2017-05-16
  • Resolved: 2006-01-04
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
6 b43Fixed
Description
Prior to version 1.2 of the JMX Specification, the Timer service was defined to throw an exception if a notification was scheduled for a time in the past.  Starting from version 1.2, the more logical behaviour of sending the notification immediately in this case was introduced.  However, some of the documentation for javax.management.timer.Timer still reflects the old behaviour.  In particular, the Notes in the class documentation include one that says (in so far as it can be deciphered) that past-time notifications will be ignored, and the @throws documentation for the IllegalArgumentException says it is thrown for a past date.
###@###.### 2005-03-02 19:09:58 GMT
Comments
EVALUATION Clarify the expected behavior for past-time notifications: If a timer notification is scheduled for a time in the past a notification should be sent immediately. ###@###.### 2005-04-19 15:05:08 GMT Spell out in the throws clause of all the Timer.addNotification methods that IllegalArgumentException is thrown when the supplied Date is null. ###@###.### 2005-06-07 13:00:32 GMT
19-04-2005