Timeout for execution of JobSchedulerNotificationCheckHistoryJob

Current Situation

• The JobSchedulerNotificationCheckHistoryJob job reads data from the JobScheduler tables (SCHEDULER_HISTORY, SCHEDULER_ORDER_HISTORY, SCHEDULER_ORDER_STEP_HISTORY).
• If the JobScheduler Master accesses the same tables at the same time then these tables may be locked and the JobScheduler Master and this job might not respond if the DBMS has no or has limited support for deadlock detection as e.g. MySQL with the InnoDB engine.

Desired Behaviour

• The execution time of the JobSchedulerNotificationCheckHistoryJob job is adjustable to resolve deadlock situations without DBMS support.
• Introducing the two new job parameters:
  • max_execution_time (in seconds)
    • if this period is exceeded then the job ends with a timeout exception.
    • default value: -1 (unlimited)
  • max_execution_time_exit (in seconds)
    • in case of the timeout exeption - this parameter specifies the maximum time allowed to rollback the transaction and to disconnect from the database.
    • default value: 5

Applicable JobScheduler Releases

• The following patches are deprecated and removed for download:
  • 1.10.6: patch_for_jitl_485_on_1.10.6.zip
  • 1.10.7-1.10.10: patch_for_jitl_485_on_1.10.7-1.10.10.zip
• Please use instead a patch provided with JITL-516