Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.12, 1.13.3
-
None
-
None
Description
Current Situation
- In the JOC Cockpit History View and Daily Plan View the start and end time of the jobs and orders shows a wrong date.
- This problem shows an erratic behavior as it cannot be determined if and when this happens.
- The root cause of this problem is the fact that JOC Cockpit makes use of a connection pool. to access the database. Some connections are established immediately at start-up of JOC Cockpit, some are established later on on demand. If the server that operates JOC Cockpit is running in a non-UTC time zone then the initial connections will consider this time zone and connections that are established later on will use the UTC time zone.
How to Reproduce
- Start/restart the JOC Cockpit 1.13.3.
- Run an order, e.g., createDailyPlan.
- View the history from the history tab.
Desired Behavior
- The start and end time of the job and order history should be the same for the task and order log.
- To this aim the JOC Cockpit should be started with the -Duser.timezone=UTC setting.
Workaround
Reinstall JOC
- Batch-installation: Use
<entry key="jettyOptions" value="-Duser.timezone=UTC"/>
in the parameter file joc_install.xml
- Dialog-installation: Enter -Duser.timezone=UTC in the "Further Java Options" input field of the Jetty Configuration form.
Without reinstallation
- Windows: Open ./service/sos_jocw.exe, navigate to "Java" tab and add -Duser.timezone=UTC to the "Java Options" text area.
- Linux: Open etc/default/joc and add -Duser.timezone=UTC to the "JAVA_OPTIONS"