WINTIME_RESYNC_PERIOD

Summary

This attribute defines the interval (in seconds) at which iProcess Engine checks to see if its timestamps are in step with Windows system time.

Applies To

The attribute must be set for ALL processes.

Permissible Values

An integer that is greater than or equal to 0. If this attribute is set to 0 then no checks are performed.

Default Value

The attribute is assigned the following default value when the iProcess Engine node is installed.

Machine ID	Process	Instance	Value
0	ALL	0	300

Notes

The iProcess Engine node records audit trail timestamps to microsecond precision and sorts the audit trail based on the timestamp.

Because the Windows system timer only returns time to millisecond accuracy, the iProcess Engine node uses two system timers to generate its audit trail timestamps - the system timer (GetSystemTime function) and a high-resolution performance counter (QueryPerformanceCounter function) which can be used to provide extra precision. However, it has been found that these timers do not keep in step with each other, and can diverge by up to several seconds for days. This can result in two problems:

•

iProcess Engine timestamps do not correspond to the current Windows time when they are generated.

• If BG processes are started at different times, any timestamps they generate will be out of synchronization with each other. This can result in audit trail entries appearing out of order.

To deal with these problems, you can use the WINTIME_RESYNC_* process attributes to configure how iProcess Engine synchronizes its timestamps with Windows system time.

Every WINTIME_RESYNC_PERIOD seconds iProcess Engine checks to see if its timestamps are in step with Windows system time. If the timestamps differ by more than WINTIME_RESYNC_TOLERANCE milliseconds iProcess Engine resynchronizes its timers with Windows system time. iProcess Engine processes are given WINTIME_RESYNC_NOTICE seconds notice before the resynchronization takes place.