JobScheduler Monitoring Interface - SystemNotifier job fails with a NullPointerException

Current Situation

• When an error reoccurrs in the same job node for which a notification has already been sent and the notification is not configured to use the <NotifyRepeatedError> element - in some cases the SystemNotifier job can fails with a NullPointerException.

Desired Behavior

• The SystemNotifier should run without errors regardless of whether a <NotifyRepeatedError> declared or not.

Workaround

• Configure a <NotifyRepeatedError> on the respected <JobChain> configuration item

Test Instructions

• Test configuration:
  • unzip the TEST-JITL-594.zip file to the $scheduler_data/config/live directory
  • make shure what the sos/notification/SystemNotifier job runs manually (MonitorSystem order is without run time)
  • use provided configuration (notification.xml) to monitor the JITL-594/test job chain
• Test execution:
  • run the JITL-594 job chain (start the Start order)
    • the order will be suspended
  • run the sos/notification/SystemNotifier job chain
    • an error notification will be send
  • change the script element of the JITL-594/job_100 job from

    <![CDATA[
    rem ping -n 200 localhost
    exit 1
    ]]>
    

    to

    <![CDATA[
    ping -n 200 localhost
    rem exit 1
     ]]>
    

  • resume the suspended JITL-594 order
  • run again the sos/notification/SystemNotifier job chain
    • job fails with a NullPointerException