Distributed Orders with a start time after 2023-01-23 20:13:53Z are not started

Current Situation

• Distributed Orders running in an Active Master Cluster with a next start time after 2023-01-23 20:13:53,999Z are not started.
• In JOC Cockpit users observe the start time indication: "Next start: never".
• Delimitation
  • This problem occurs for orders that include a start time rule (<run-time>), this does not occur for ad hoc orders that are manually added for immediate execution.
  • This problem does not occur for orders in a Passive Master Cluster and Standalone Master.

Desired Behavior

• Distributed Orders should start according to the calculated next start time.

Workaround

• Change the Active JobScheduler Master Cluster to a Passive JobScheduler Master Cluster (see below wiki page).

Patch

• A patch is available for JobScheduler version 1.13.9 to 1.13.17
  • Linux:
    • Download https://download.sos-berlin.com/JobScheduler.1.13/jobscheduler_linux.patch.JS-2037.tar.gz
    • Extract the archive to SCHEDULER_HOME/lib
  • Windows:
    • Download https://download.sos-berlin.com/JobScheduler.1.13/jobscheduler_windows.patch.JS-2037.zip
    • Extract the archive to SCHEDULER_HOME\bin