-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
Given
- Camunda engine 1 in Timezone 1
- Camunda Engine 2 in Timezone 2
- Database in Timezone 3
When
- I store some date value via Java API of Camunda engine 1 (e.g. task due date)
- I retrieve the saved date via Java API of Camunda engine 2
Then
- Two dates represent the same time instance
So that
- Timezones are correctly working in the cluster
Hints
- Research is needed, what should be done for such operations to be processed correctly and results are documented if needed
- In theory such types of situations must be managed by JDBC Driver
- May be some parameters must be passed in JDBC URLs