In nested job chains wrong values for the "end_time" column are created for the last job chain node

Current Situation

• If a nested job chain includes more than one job chain (indicated by the <job_chain_node.job_chain_ nodes> element of the job chain configuration), then after execution of the last included job chain a wrong value for the end_time column is added to the order history (table SCHEDULER_ORDER_HISTORY).

How to Reproduce

• Deploy the attached example JS-1797.zip in the live folder.
• Run the chain_nested order
• Compare the end_time and start_time column values for the JS-1797/chain_2 job chain in the SCHEDULER_ORDER_HISTORY table
  • START_TIME and END_TIME show equal values
    • See attached scheduler.log for history id 1342
      • insert - row 135
      • update - row 230

Desired Behavior

• The end_time for all executions of job chains included with a nested job chain should be correct.

Test Instruction

Test Configuration

• Open JOE and create two order jobs.
• Then create two job chains with one job each.
• After that create a nested job chain and add the above two job chains in the nodes of this nested job chain.

Test Execution

• Login on to the JOC cockpit.
• Add order to the nested job chain created.
  • Negative test: After execution of last included job chain includes a wrong value for the end_time column i.e. the value for _START_TIME and END_TIME show equal values.
  • Positive test: After execution of last included job chain includes a correct value for the end_time column i.e. the value for _START_TIME and END_TIME DOES NOT show equal values.