Hi Steve, I looked at the code and don't see such a race there. But I noticed that nextExecutionTime() uses U.currentTimeMillis() as start time, which looks suspicious. Do you have a test that reproduces the issue?
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Race-condition-in-IgniteScheduler-nextExecutionTime-tp3261p3266.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
