Notification sometimes does not notify errors when order is suspended

Current Situation

When a job chain node is suspended on error and the job in this node fails. No notification is send when the job check_history has been startet before order is suspended.

Desired Behavior

When a job chain node is suspended on error and the job in this node fails a notification should be send.

Testcase for 1.10

• unzip jitl-516.zip to $scheduler_data/config/live
• copy SystemMonitorNotification_MonitorSystem.xml to {{config\notification }}
• modify SystemMonitorNotification_MonitorSystem.xml
  • NotificationCommand: D:/scheduler_notification.txt
  • JobChain name: if you rename the job chain

Test 1

• start order jit-516/Start_1
• while running before suspending
  • start job CheckHistory
  • start SystemNotifier
  • After order is suspended
    • start CheckHistory
    • start SystemNotifier
      ==> !!! no notification is send (check the file scheduler_notifcation.txt)

Test 2:

• start order jitl-516/Start_1
• after order is suspended
  • start CheckHistory
  • start SystemNotifier
    ==> !!! notification is send (check the file scheduler_notifcation.txt)

Applicable JobScheduler Releases

A patch is available for download with JobScheduler releases:

• JobScheduler 1.10.6
  • Download the patch patch_for_jitl_485_jitl_516_on_1.10.6.zip
  • Extract the patch_for_jitl_485_jitl_516_on_1.10.6.zip to any location
  • Copy content of the jobs folder (patch_for_jitl_485_jitl_516_on_1.10.6/SCHEDULER_DATA/jobs) to
    • {$scheduler_data}/jobs
  • Copy content of the db folder (patch_for_jitl_485_jitl_516_on_1.10.6/SCHEDULER_HOME/db) to
    • {$scheduler_home}/db
  • Stop JobScheduler
  • Execute on the command line shell
    • {$scheduler_home}/install/scheduler_install_tables(.sh)|(.cmd) scheduler_mon_sysresults.sql
  • Remove patch {$scheduler_home}/lib/patches/patch_for_jitl_485_on_1.10.6.jar if exists
  • Copy patch_for_jitl_485_jitl_516_on_1.10.6.jar (patch_for_jitl_485_jitl_516_on_1.10.6/SCHEDULER_HOME/lib/patches) to
    • {$scheduler_home}/lib/patches
  • Start JobScheduler
• JobScheduler 1.10.7-1.10.10
  • Download the patch patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10.zip
  • Extract the patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10.zip to any location
  • Copy content of the jobs folder (patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10/SCHEDULER_DATA/jobs) to
    • {$scheduler_data}/jobs
  • Copy content of the db folder (patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10/SCHEDULER_HOME/db) to
    • {$scheduler_home}/db
  • Stop JobScheduler
  • Execute on the command line shell
    • {$scheduler_home}/install/scheduler_install_tables(.sh)|(.cmd) notification_sysresults.sql
  • Remove patch {$scheduler_home}/lib/patches/patch_for_jitl_485_on_1.10.7-1.10.10.jar if exists
  • Copy patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10.jar (patch_for_jitl_485_jitl_516_on_1.10.7-1.10.10/SCHEDULER_HOME/lib/patches) to
    • {$scheduler_home}/lib/patches
  • Start JobScheduler
• JobScheduler 1.12.7
  • Download the patch patch-20190227-JITL-516-JITL-549-1.12.7.zip
  • Extract the patch-20190227-JITL-516-JITL-549-1.12.7.zip to any location
  • Copy content of the jobs folder (patch-20190227-JITL-516-JITL-549-1.12.7/SCHEDULER_DATA/jobs) to
    • {$scheduler_data}/jobs
  • Copy content of the db folder (patch-20190227-JITL-516-JITL-549-1.12.7/SCHEDULER_HOME/db) to
    • {$scheduler_home}/db
  • Stop JobScheduler
  • Execute on the command line shell
    • {$scheduler_home}/install/scheduler_install_tables(.sh)|(.cmd) notification_sysresults.sql
  • Copy patch-20190227-JITL-516-JITL-549-1.12.7.jar (patch-20190227-JITL-516-JITL-549-1.12.7/SCHEDULER_HOME/lib/patches) to
    • {$scheduler_home}/lib/patches
  • Start JobScheduler