ClusterTimer, Updated time skew

I have seen in the logs this Info:

ClusterTimer, Updated time skew. New skew is -3 Old skew was 3 and Urzeit is 1334181600000

Since I am as curious as a cat, I have searched and found out that this is logged by com.bea.wli.timer.TimeSkewSynchronizer,

running a TimeSkewSynchronizerTask which in turn uses a ClusterTimerService which uses a ClusterTimerPersistenceStore to persist the Urzeit (apart from being a mythological archetype, it's also a universal time reference).

more to come...