Timer handlers empty and run as part of daemon handlers

[jheusser]

Maybe introduced as part of a refactor, but Timer handlers are run together with Daemon handlers (which is never if you are always busy) due to this switch case. Then consequently, the call to runTimerHandlers is empty in the hot method. Can submit a PR if you like.

[peter-lawrey]

Please offer a pull request. The higher priority handlers shouldn't be
busy long, but this might be longer than the timer expects.

On 8 October 2015 at 12:31, Jonathan Heusser notifications@github.com
wrote:

Maybe introduced as part of a refactor, but Timer handlers are run
together with Daemon handlers (which is never if you are always busy) due
to this switch
https://github.com/OpenHFT/Chronicle-Threads/blob/master/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java#L232
case. Then consequently, the call to runTimerHandlers is empty in the hot
method
https://github.com/OpenHFT/Chronicle-Threads/blob/master/src/main/java/net/openhft/chronicle/threads/VanillaEventLoop.java#L123.
Can submit a PR if you like.

—
Reply to this email directly or view it on GitHub
#3.

[peter-lawrey]

This was fixed in January, I am sorry for taking so long to close this.