AAI fails to restart. ERROR [JammerManager] Interrupted: com.termalabs.server.cache.UncorrectedCurrentStateTableException: Unable to read CurrentState table

Products

• Automic Automation Intelligence

Issue/Introduction

AAI fails to restart after a shutdown. 

The following error is present in the logs:

WARN  [CommonVendorImpl] Releasing write lock (jammer (first time)); held time: 0:05:57.0; waiting: 0

ERROR [JammerManager] Interrupted: com.termalabs.server.cache.UncorrectedCurrentStateTableException: Unable to read CurrentState tabl

        at com.termalabs.server.cache.CurrentStateVendorImpl.repairCurrentStates(CurrentStateVendorImpl.java:342)

        at com.termalabs.server.cache.CurrentStateVendorImpl.initializeAllCurrentStates(CurrentStateVendorImpl.java:312)

        at com.termalabs.server.system.JammerManager.doFirstTimeProcessing(JammerManager.java:402)

        at com.termalabs.server.system.JammerManager.run2(JammerManager.java:309)

        at com.termalabs.server.system.JammerManager.run(JammerManager.java:239)

        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)

Caused by: com.termalabs.common.datastore.DataAccessException: Error while executing query: "from CurrentState cs left join fetch cs.mostRecentRun left join

        at com.termalabs.common.connection.hibernate.RichQueryCommon.executeAndTime(RichQueryCommon.java:1047)

        at com.termalabs.common.connection.hibernate.RichQueryCommon.list(RichQueryCommon.java:969)

        at com.termalabs.server.hibernate.RichQuery$CollectionQuery.asSetUnfiltered(RichQuery.java:175)

        at com.termalabs.server.hibernate.RichQuery$CollectionQuery.asSet(RichQuery.java:155)

        at com.termalabs.server.hibernate.jaws.HibernateCurrentStateData.getAllCurrentStates(HibernateCurrentStateData.java:81)

        at com.termalabs.server.cache.CurrentStateVendorImpl.getAllCurrentStates(CurrentStateVendorImpl.java:350)

        ... 7 in common

Environment

Release : 6.2.X

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Cause

Configuration

Resolution

Check if database maintenance is taking longer than a few hours. Example in the log:

INFO [DBMaintWorker] Running DB Maintenance
INFO [DBMaintWorker] Finished DB Maintenance (0:07:23.2 elapsed) 

If it does, make sure the maintenance loader runs at least 4 hours before the business day.

In most cases, if there are a lot of records for deletion, database maintenance will catch up, and the issue will be resolved. 

If that does not resolve the issue, open a case with Broadcom Support and provide full set of log files.