[JobStreamVendorImpl] initializing all job streams ERROR [JammerManager] Interrupted: com.termalabs.common.MissingJobException: No such job: UUID[8a6480d25187665101518d19c7f94efb]

Products

• Automation Analytics & Intelligence

Issue/Introduction

Unable to login to the AAI thick client, and errors below are seen in the jaws.log file:

 

   ERROR [JammerManager] Interrupted: com.termalabs.common.MissingJobException: No such job: UUID[XXXXXXX]
    at com.termalabs.server.cache.SchedulerVendorImpl.getJobById(SchedulerVendorImpl.java:1454)
    ... 2 skipped
    at java.lang.reflect.Method.invoke(Method.java:498)
    at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:50)
    at com.sun.proxy.$Proxy87.getJobById(Unknown Source)
    at com.termalabs.server.cache.JobStreamVendorImpl.filterAndAttachCachedJSJs(JobStreamVendorImpl.java:489)
    at com.termalabs.server.cache.JobStreamVendorImpl.initializeJobStream(JobStreamVendorImpl.java:455)
    at com.termalabs.server.cache.JobStreamVendorImpl.createJobStreamsMap(JobStreamVendorImpl.java:411)
    at com.termalabs.server.cache.JobStreamVendorImpl.createJobStreamsMapIfNeeded(JobStreamVendorImpl.java:308)
    at com.termalabs.server.system.JammerManager.doFirstTimeProcessing(JammerManager.java:402)
    at com.termalabs.server.system.JammerManager.run2(JammerManager.java:308)
    at com.termalabs.server.system.JammerManager.run(JammerManager.java:238)
    at com.termalabs.server.system.ApplicationControllerService$2.run(ApplicationControllerService.java:268)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)

Environment

Release : 6.4.2-2

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Cause

Defect

Resolution

1) Workaround

This appears to occur after an abrupt shutdown of the AAI service, where the service had to be killed.

 

We resolved this by cleaning up these orphaned records from the database with the queries below with services stopped:

delete from JobStream_Job where jobId='XXXXXXX';

commit;

 

After restarting AAI, we saw similar errors with different job ID's so we came up with the query below to identify how many jobs were in this state and got many results:

select * from JobStream_Job where jobId in(select jobId from JawsJob where deletedTime is not NULL)

 

We then shutdown services again and ran the delete statement below to clear these up. 

delete from JobStream_Job where jobId in(select jobId from JawsJob where deletedTime is not NULL);

commit;
 

We restarted the AAI service and it was able to fully initialize and you were able to login to the AAI Thick client.

 

 

2) Final Fix

The isssue has been fixed in AAI v6.4.3.