How is the Timer class in Java sensitive to the system clock? [duplicate]

Answer 1

Looking at the source, The Timer class schedules tasks using System.currentTimeMillis(). The ScheduledThreadPoolExecutor uses System.nanoTime().

currentTimeMillis() will tend to use the OS clock, the one that tracks the current date/time. nanoTime() will tend to use a higher resolution hardware clock.

If you move your OS clock back an hour, then currentTimeMillis() could should reflect that while nanoTime() should not.

Answer 2

Timer uses System.currentTimeMillis(), which represents wall clock time and should never be used for checking relative times such as determining how long something took to run or, in this case, how long to delay before executing a task. System.currentTimeMillis() is affected by things like automatic adjustments to the system clock or even manually changing the system clock. As such, if you call it twice and check the difference between the times you get, you can even get a negative number.

System.nanoTime(), on the other hand, is specifically intended for measuring elapsed time and is what should be used for this sort of thing.

Answer 3

Timer uses System.currentTimeMillis() to determine the next execution of a task.

However ScheduledThreadPoolExecutor uses System.nanoTime().

Also nanoTime() method can only be used to measure elapsed time and is not related to any other notion of system or wall-clock time.

System.currentTimeMillis() is sensitive to system clock

System.nanoTime() is not sensitive to system clock as it measures the time elapsed.

Java Documentation: System.nanoTime()

This method can only be used to measure elapsed time and is not related to any other notion of system or wall-clock time. The value returned represents nanoseconds since some fixed but arbitrary time (perhaps in the future, so values may be negative).