We're seeing intermittent failures in DatabaseTimerServiceMultiNodeTestCase on our CI server. After recent migration to new machine, those failures became pretty much regular.

It seems that the TimedObjectTimerServiceBean deployed on client node is initially not processing any timer events - even if the test passes vast majority of events are processed on server node. Occasionally this results in all of the events being handled by the server and test failing