Offset problems when using MS SQL Azure for workflow time calculations
search cancel

Offset problems when using MS SQL Azure for workflow time calculations

book

Article ID: 380261

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

After migration of the IM database to SQL Azure we experience problems with the calculation of delays in workflows. All calculated steps have x hours additional delay. The application server is in GMT+2 timezone while Azure DB apparently only supports UTC.

We observed following warning messages in the server.log:
2024-09-07 11:15:13,725 INFO  [com.workpoint.server.ServerProperties] (pool-17-thread-1) ServerProperties.setProperty() invoked for property= calculated.db.offset.millis.WPDS, value=-7200009
2024-09-07 11:15:13,725 WARN  [com.workpoint.server.ConnectContext] (pool-17-thread-1) The time difference between the database server for DSN= WPDS and this machine has changed by 14400009ms since last computed. This may be a sign of clock drift on one of the machines, which can lead to unexpected results in Workpoint.

Cause

Release : 14.5.1
Component : CA Identity Manager

Resolution

The issue was resolved after adding the following parameter to /JBoss/standalone/deployments/iam_im.ear/config/workpoint-server.properties
force.db.offset.millis.WPDS=0

Additional Information

As this is a workpoint related issue, we have validated the above solution with them. Workpoint development reviewed this solution, and they do not have any issues or concerns with this solution.