Error seen after migrating AAI: Error running jammer sequence for schedulers: "AutoSys": com.termalabs.common.JawsException: Could not associate new runs.

Products

• Automation Analytics & Intelligence

Issue/Introduction

After migrating AAI and the AAI database server to new servers the errors below are seen in the jaws.log and alerts are not being generated.

WARN [CommonJammerSequence] Error running jammer sequence for schedulers: "AutoSys": com.termalabs.common.JawsException: Could not associate new runs.
 at com.termalabs.server.app.jobstream.run.ActiveJobStreamRunBuilderImpl.associateNewRuns(ActiveJobStreamRunBuilderImpl.java:313)
 at com.termalabs.server.app.jobstream.run.ActiveJobStreamRunBuilderImpl.associateLatestRuns(ActiveJobStreamRunBuilderImpl.java:191)
 at com.termalabs.server.system.RunCycle.runJobStreamRunBuilder(RunCycle.java:1108)
 at com.termalabs.server.system.RunCycle.compute(RunCycle.java:428)
 at com.termalabs.server.system.CommonJammerSequence.runCycle(CommonJammerSequence.java:226)
 at com.termalabs.server.system.CommonJammerSequence.runJammerSequence(CommonJammerSequence.java:159)
 at com.termalabs.server.system.JammerSequence.run(JammerSequence.java:136)
 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:750)
Caused by: java.lang.IllegalArgumentException: Adding text to an XML document must not be null
 at org.dom4j.DocumentFactory.createText(DocumentFactory.java:166)
 at org.dom4j.tree.AbstractElement.addText(AbstractElement.java:807)
 at com.termalabs.server.alerting.AlertGenerator.getDataValuesXml(AlertGenerator.java:889)
 at com.termalabs.server.alerting.AlertGenerator.createAlert(AlertGenerator.java:849)
 at com.termalabs.server.alerting.AlertGenerator.generateAndAddNewAlert(AlertGenerator.java:809)
 at com.termalabs.server.alerting.AlertGenerator.generateAndAddNewAlert(AlertGenerator.java:798)
 at com.termalabs.server.alerting.AlertGenerator.generateAndProcessSingleJobStreamAlert(AlertGenerator.java:203)
 at com.termalabs.server.alerting.AlertGenerator.generateAndProcessSingleJobStreamAlertIfNecessary(AlertGenerator.java:134)
 at com.termalabs.server.autosys.old.AutosysJobStreamManager.saveRunsAndGenerateCriticalPath(AutosysJobStreamManager.java:426)
 ... 11 in common

Environment

Release : 6.4.2

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Resolution

When migrating AAI to a new server, you must copy over the .jawskey file from the <install dir>/jboss/standalone/configuration directory on the original server to the new server before starting up AAI.

 

In this scenario AAI was started before the .jawskey file was generated, and the schedulers were configured through the Admin->Schedulers page which caused a mismatch in decryption details between the database and the .jawskey file, even after copying over the original .jawskey.

 

In order to resolve this issue we suggested restoring the AAI backup with the original .jawskey file from the <install dir>/jboss/standalone/configuration directory on the original server already in place on the new server.

 

This allowed AAI to start up clean and the error was no longer seen.