Either you’re debugging and hitting break points, garbage collection is taking 10 seconds, auto backups are taking 10 seconds, or you’re experiencing regular 10 second movements in the system clock.
It’s there to warn you that the system is slower than it should be in some way…
(The idea may be a bit flawed… But we’ve had an influx of people running ignition in VMs with weird things happening to their system clock or long pauses to the system happening.)
Just FYI ive pulled my ignition server out of virtualisation and put it on a physical machine. Had no problems since then Kevin. Ill try it again after the next upgrade on the VM but im just glad to be back up and running.
The really treacherous thing about Dan’s VM situation is that it turns out the clock isn’t really drifting by any dramatic amount, but that the System.currentTimeMillis() call is sporadically returning timestamps from the future (hours, days) and then returning back to normal behavior immediately after.