I would like to clarify something about TimerTask. When you have the code below:
timer.schedule(task, 60000);
where the task is scheduled to ru
No, it is going to invoke the run method of this task in exactly 60 seconds. If task.cancel()
returns false
, that could mean 3 things:
Hence, if you are certain that you call cancel
before 60 seconds after scheduling the task, you could potentially either call it several times, and get a result from a subsequent cancel
, OR you are calling cancel on a different task.
You can achieve a desired functionality with:
ScheduledExecutorService.schedule( callable, delay, timeunit )
Reasons why ScheduledExecutorService are is a preferred way are outlined here:
Timer can be sensitive to changes in the system clock, ScheduledThreadPoolExecutor isn't
Timer has only one execution thread, so long-running task can delay other tasks. ScheduledThreadPoolExecutor can be configured with any number of threads. Furthermore, you have full control over created threads, if you want (by providing ThreadFactory)
runtime exceptions thrown in TimerTask kill that one thread, thus making Timer dead :-( ... i.e. scheduled tasks will not run anymore. ScheduledThreadExecutor not only catches runtime exceptions, but it lets you handle them if you want (by overriding afterExecute method from ThreadPoolExecutor). Task which threw exception will be canceled, but other tasks will continue to run.
I don't know why your code returns false
.
The following code prints true
.
import java.util.Timer;
import java.util.TimerTask;
public class Test {
public static void main(String[] args) {
Timer timer = new Timer();
TimerTask task = new TimerTask() {
@Override
public void run() {
System.out.println("hi");
}
};
timer.schedule(task, 60000);
System.out.println(task.cancel());
}
}
If the last println
is commented, the program prints hi
.