HashedWheelTimer and changing system time

[Christian Migowski]

It is not broken, just like I said, your test is rather strange
(changing time back and forth).
I just ran your test, here the timeout fires in the next round (i.e.
after an additional 30 seconds), which is IMHO fair enough under this
circumstances.
If you change time in just one direction (as it would happen with DST
or time servers), it works as expected.

regards,
christian!


On Thu, Jun 24, 2010 at 9:32 AM, Evgeniy Devyatyh <devyatyh at gmail.com> wrote:
>
>>>it is a strange test
> Myabe, it's just synthetic test.
>
> But anyway why when timeout expired (HashedWheelTimeout(deadline: 656 ms
> ago, ) ) timer task not run?
>
> Ok, nanoTime is broken, but currentTimeMillis broken too because if Windows
> synchronize system clock or change time for daylight savings all timer tasks
> may not run?
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/HashedWheelTimer-and-changing-system-time-tp5216326p5216556.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>