[OAK-3645] RDBDocumentStore: server time detection for DB2 fails due to timezone/dst differences

• Type: Technical task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.24, 1.2.8, 1.3.10
• Fix Version/s: 1.0.26, 1.2.10, 1.3.14, 1.4
• Component/s: rdbmk
• Assignee: Julian Reschke
• Reporter: Julian Reschke
• Created: 17/Nov/15 11:12
• Updated: 02/Mar/16 15:13
• Resolved: 12/Jan/16 11:51

Description

We use CURRENT_TIMESTAMP(4) to ask the DB for it's system time.

Apparently, at least with DB2, this might return a value that is off by a multiple of one hour (3600 * 1000ms) depending on whether the OAK instance and the DB run in different timezones.

Known to work: both on the same machine.

Known to fail: OAK in CET, DB2 in UTC, in which case we're getting a timestamp one hour in the past.

At this time it's not clear whether the same problem occurs for other databases.