We will need to go back to System.nanoTime().
there are some kernel versions that don't play well with timing. nanosleep, usleep or
any other native sleep has ticking problems.
Or maybe.. we keep native-timers, and let the user decide on flush-on-sync. That would
save some cpu cycles.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235503#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...