[
https://issues.apache.org/jira/browse/OAK-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093628#comment-15093628
]
Tomek Rękawek commented on OAK-3645:
------------------------------------
Yes, apparently Derby doesn't know anything about timezones and therefore
there's no way to get a correct value. Falling back to the default "" seems
like a good approach.
> 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: Tomek Rękawek
> 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)
