Plugin throws error "duplicate key value violates unique constraint "scheduler_mn_uniq"

Current Situation

• The FactNotification Plugin throws the following error:

  .22 01:01:55.534 com.sos.jitl.reporting.plugin.FactNotificationPlugin [ERROR] - process: java.lang.Exception: process: com.sos.hibernate.exceptions.SOSHibernateObjectOperationException: could not execute statement: 0 ERROR: duplicate key value violates unique constraint "scheduler_mn_uniq"
    Detail: Key ("SCHEDULER_ID", "ORDER_HISTORY_ID", "STEP", "TASK_ID", "STANDALONE")=(SOSJS1, 106448, 1, 157264, 0) already exists. [n/a] 
  

• This error can occur if the com.sos.jitl.notification.jobs.result.StoreResultsJobJSAdapterClass monitor is activated.
  • See JobScheduler Monitoring Interface - Store parameters to database

Desired Behavior

• The FactNotification Plugin should not throw errors.

Test Instruction

• unzip JITL-549.zip to any location
• define global monitor in the $scheduler_data/config/scheduler.xml
  • add content of the JITL-549/config/scheduler.xml <plugin java_class="com.sos.scheduler.plugins.globalmonitor.GlobalMonitorPlugin"> to your scheduler.xml configuration
  • adjust <param name="configuration_directory" value="..." />
• copy JITL-549/config/live/global_notification_store_results.monitor.xml to $scheduler_data/config/live
• adjust $scheduler_data/config/notification/SystemMonitorNotification_MonitorSystem.xml to notify all job chains
  • see example
• restart the JobScheduler
• run some job chains and check the scheduler.log for the "duplicate key" exception

Applicable JobScheduler Releases
A patch is available for download with JobScheduler releases:

• JobScheduler 1.12.7
  • The patch is available with JITL-516
• JobScheduler 1.12.8
  • Download the patch patch-20190301-JITL-549-1.12.8.zip
  • Extract the patch-20190301-JITL-549-1.12.8.zip to any location
  • Stop JobScheduler
  • Copy patch-20190301-JITL-549-1.12.8.jar to {$scheduler_home}/lib/patches
  • Start JobScheduler