[
https://issues.apache.org/jira/browse/OAK-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved OAK-3645.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3.14
1.2.10
1.0.26
trunk: http://svn.apache.org/r1724210
1.2: http://svn.apache.org/r1724211
1.0: http://svn.apache.org/r1724212
(thanks to [~tomek.rekawek]] who did most of the work)
> RDBDocumentStore: server time detection for DB2 fails due to timezone/dst
> differences
> -------------------------------------------------------------------------------------
>
> Key: OAK-3645
> URL: https://issues.apache.org/jira/browse/OAK-3645
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: rdbmk
> Affects Versions: 1.3.10, 1.2.8, 1.0.24
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Fix For: 1.0.26, 1.2.10, 1.3.14
>
> Attachments: OAK-3645-jr.patch, OAK-3645.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
