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: 6730507
Votes 0
Synopsis java.util.Timer schedule delay Long.MAX_VALUE causes task to execute multiple times
Category java:classes_util
Reported Against b30
Release Fixed 7(b34)
State 10-Fix Delivered, bug
Priority: 4-Low
Related Bugs
Submit Date 28-JUL-2008
Description
Passing a very large delay, e.g. Long.MAX_VALUE, as a parameter to one of the four schedule(AtFixedRate) methods can cause the task to be executed again and again, when clearly this is not the intention.

 For Example:
   timer.scheduleAtFixedRate(t, 0L, Long.MAX_VALUE);
 causes the task, t, to be executed over and over again.

A period of Long.MAX_VALUE should cause a periodic task to "never" execute twice.
Posted Date : 2008-07-28 15:19:46.0
Work Around
N/A
Evaluation
http://hg.openjdk.java.net/jdk7/tl/jdk/rev/659b74b5373f
Posted Date : 2008-08-07 13:44:01.0
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang