Updates for the Daily Plan and inventory for JOC Cockpit fail when a period interval end/start for a job or order is used

Current Situation

• When an order or a job is configured for a repeat interval end/start starting from 00:00 then
  • the CreateDailyPlan job raises a SQLIntegrityConstraintViolationException
  • the inventory of jobs and orders raises the same exception
• A restart of JobScheduler is required to see changes in JOC.

Impact

• The result of this is,
  • the daily plan will not be updated.
  • changes of the configuration (inventory) are not reflected with the JOC Cockpit GUI
    • if a new folder is created with an order or job that is hit by the above problem. Should any other objects such as jobs or job chains be created before the offending job or order is created then they will be displayed.
    • if an existing job or orders is modified to be hit by the above problem then no updates for this job or order are displayed with JOC Cockpit.
• Delimitation
  • This problem does not effect the start time of jobs and order but the visibility of updates with JOC Cockpit.

Desired Behavior

• No SQLIntegrityConstraintViolationException should be raised when creating the daily plan and when updating the inventory.

Test Cases

• Create an order or job with the following run-time:

    <run_time  let_run="yes">
          <weekdays >
              <day  day="1 2 3 4 5 6 7">
                  <period  repeat="00:05" begin="00:00" end="24:00"/>
              </day>
          </weekdays>
      </run_time>
  

• Create an order or job with the following run-time:

  <run_time >
          <weekdays >
              <day  day="1 2 3 4 5 6 7">
                  <period  single_start="00:00"/>
              </day>
          </weekdays>
      </run_time>
  

• Perform the following check:
  • Use the Advanced Search function in the Daily Plan view for an interval of more than 32 days.
  • For each day two entries are found in the daily plan (from the above two run-times).
  • The run-time for today shows two entries.
  • There are no double entries.
  • There are no missing entries.
  • Change the single start time to 01:00:00
  • Check whether the daily plan is updated correctly.

Workaround

Use start/start repeat interval (change repeat to absolute_repeat

  <run_time  let_run="yes">
        <weekdays >
            <day  day="1 2 3 4 5 6 7">
                <period  absolute_repeat="00:05" begin="00:00" end="24:00"/>
            </day>
        </weekdays>
    </run_time>

Patch

• Download the patch from here
• Unzip the patch file
• Store the extracted .jar file to $SCHEDULER_HOME/lib/patches