Scheduler not jamming - com.termalabs.server.cache.jobrun.DuplicateJobRunException: Duplicate JobRun for job

Products

• Automic Automation Intelligence

Issue/Introduction

TheJammer is failing on a scheduler.

 

2021-04-16 13:18:35,853 INFO  [RunCycle] Jammer phase for Scheduler3,Scheduler4 started
2021-04-16 13:18:50,637 WARN  [RunCycle] Jammer failed for scheduler: PC3: com.termalabs.server.cache.jobrun.DuplicateJobRunException: Duplicate JobRun for job: JOBNAME/139886, extRunId: 545081348, jawsNumberRetries: 1
        New run startTime: 2021/04/15 20:21:29.000 CDT, endTime: 2021/04/15 21:09:42.000 CDT, lastJobState: SUCCESS
        Dup run startTime: 2021/04/15 20:00:20.000 CDT, endTime: 2021/04/15 21:09:42.000 CDT, lastJobState: SUCCESS

        at com.termalabs.server.cache.jobrun.JobRunChecker.checkJobRun(JobRunChecker.java:115)
        at com.termalabs.server.cache.jobrun.AutosysRunUpdateBuilderImpl.updateJobRun(AutosysRunUpdateBuilderImpl.java:101)
        at com.termalabs.server.autosys.jammer.AutosysEventProcessorImpl.updateAndTrackRun(AutosysEventProcessorImpl.java:670)
        at com.termalabs.server.autosys.jammer.AutosysEventProcessorImpl.processRun(AutosysEventProcessorImpl.java:407)
        at com.termalabs.server.autosys.jammer.AutosysEventProcessorImpl.processEvent(AutosysEventProcessorImpl.java:275)
        at com.termalabs.server.publications.events.EventCollectingAutosysEventProcessor.processEvent(EventCollectingAutosysEventProcessor.java:30)
        at com.termalabs.server.autosys.jammer.AutosysNewJammer.convertEventsToRuns(AutosysNewJammer.java:690)
        at com.termalabs.server.autosys.jammer.AutosysNewJammer.processEvents(AutosysNewJammer.java:581)
        at com.termalabs.server.autosys.jammer.AutosysNewJammer.processRuns(AutosysNewJammer.java:333)
        at com.termalabs.server.system.RunCycle$JammerRunner.runJammer(RunCycle.java:934)
        at com.termalabs.server.system.RunCycle$JammerRunner.run(RunCycle.java:916)
        at com.termalabs.server.system.RunCycle.compute(RunCycle.java:281)
        at com.termalabs.server.system.CommonJammerSequence.runCycle(CommonJammerSequence.java:225)
        at com.termalabs.server.system.CommonJammerSequence.runJammerSequence(CommonJammerSequence.java:158)
        at com.termalabs.server.system.JammerSequence.run(JammerSequence.java:141)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

Environment

Release : 6.0.2

Component : AUTOMIC AUTOMATION INTELLIGENCE INTEGRATION FOR BMC

Cause

DE500328 raised to investigate root cause and mitigation.

Resolution

1. Take the affected scheduler offline.

2. Restarted AAI.

3. After it was fully initialized we brought the scheduler back online.

 

A fix for this problem is included in the 6.3.0-1 release. 

https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA/latest/AAI%20Guides/Content/AAI_Topics/Release_notes_6_3_0-1/Release_Notes_6_3_0-1.htm#link2

• • Resolved an issue in the JobRunChecker that resulted in a DuplicateJobRunException.

    AAI now catches the exception when updating the job run and increases the jawsNumberRetrys value the same as when submitting a new run.