AAI stops processing data after the JAWS AAI/admin password has been changed from the default in 6.0.x and later.
search cancel

AAI stops processing data after the JAWS AAI/admin password has been changed from the default in 6.0.x and later.


Article ID: 190569


Updated On:


Automation Analytics & Intelligence



1) There are issues with micro-services starting up in environments where the JAWS AAI/admin password has been changed from the default and you see the following in the telemetryService.log file:

INFO  [TelemetryServlet] Starting TelemetryServlet on {hostname} with PID 134882 (started by jawsuser in <InstallDir>/jboss)
INFO  [TelemetryServlet] No active profile set, falling back to default profiles: default
INFO  [ServiceDatabaseUtils] Building name based data source
INFO  [ServiceDatabaseUtils] Testing data source connection retrieval
INFO  [ServiceDatabaseUtils] Successful data source connection retrieval

And there is not the following (the lines below will not be present in the logs)

INFO  [TelemetryService] Starting telemetryService
INFO  [TelemetryConfiguration] Initializing telemetry configuration
INFO  [TelemetryConfiguration] Done Initializing telemetry configuration
INFO  [TelemetryService] Scheduling telemetry recording every day at hour 0, minute 0 local time
INFO  [TelemetryServlet] Started TelemetryServlet in 733.484 seconds (JVM running for 758.155)

2) If you see modules in the deployments folder stuck in isdeploying -

/jaws/current/jboss/standalone/deployments 253$ ls -l  *isdeploying
-rw-r--r-- 1 jaws jaws 12 Mar 10 14:11 activemq.war.isdeploying
-rw-r--r-- 1 jaws jaws 33 Mar 10 14:11 alerts-service-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws 50 Mar 10 14:11 appLandscapeEventCreatorService-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws 39 Mar 10 14:11 applicationLandscape-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws 28 Mar 10 14:11 customConditionGenerator.war.isdeploying
-rw-r--r-- 1 jaws jaws  8 Mar 10 14:11 help.war.isdeploying
-rw-r--r-- 1 jaws jaws  8 Mar 10 14:11 jaws.ear.isdeploying
-rw-r--r-- 1 jaws jaws 10 Mar 10 14:11 jconn4.jar.isdeploying
-rw-r--r-- 1 jaws jaws 37 Mar 10 14:11 simulation-service-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws 39 Mar 10 14:11 subscription-service-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws 36 Mar 10 14:11 telemetry-service-6.0.0-SNAPSHOT.war.isdeploying
-rw-r--r-- 1 jaws jaws  9 Mar 10 14:11 terma.war.isdeploying


You may see log messages like:

INFO [JawsRestApiCaller] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again


You will also see the error below in the server.log 24 hours after either changing the admin password or upgrading from a 5.x release.:

ERROR [org.jboss.as.controller.OperationContextImpl] WFLYCTL0348: Timeout after [86400] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),


Release : 6.0.0





1. Stop the AAI application. Make sure that all processes are gone.

2. Remove the following files -

  • jboss/standalone/deployments/*.failed
  • jboss/standalone/deployments/*.*deploy*
  • jboss/standalone/deployments/*.old
  • jboss/standalone/tmp*
  • jboss/standalone/data/*

3. Bring up the Configuration tool

  1. Select the Params tab
  2. Change the Show drop-down to hidden named parameters
  3. Select Show hidden param
  4. Enter servicePass in the box
  5. Select OK
  6. Put the updated password for the admin user in the Value column
  7. Select Apply and OK

4. Start the AAI application

Additional Information

If the issue still persists after the Solution is applied, open a case with Support and submit the full set of log files.