The Simulation Service takes logn to start: login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
search cancel

The Simulation Service takes logn to start: login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again

book

Article ID: 375340

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

The Simulation Service is taking a lot of time to completely start up. The messages in simulation.log is present.

 

INFO  [SimulationServlet] Starting SimulationServlet using Java 1.8.0_381 on ATSAAIPRDSTB1 with PID 6704 (started by ATSAAIPRDSTB1$
FINE  [SimulationServlet] Running with Spring Boot v2.7.18, Spring v5.3.31
INFO  [SimulationServlet] No active profile set, falling back to 1 default profile: "default"
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
 INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
2INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
2INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
DEBUG [JawsRestApiCallerForSIM] Successfully updated JAWS server cookie.
DEBUG [SimulationConfiguration] testMode is: false
INFO  [SimulationService] Starting Simulation Service

Cause

Product: Automation Analytics & Intelligence v6.x

Resolution

The pause between the two red lines below the messages in blue are expected behavior. The messages mean that the Simulation service keeps trying to log in to the AAI via REST API but the AAI has not finished initializing. Basically, the Simulation service will not complete starting up until AAI started completely and the Simulation service is able to log in.

 

INFO  [SimulationServlet] Starting SimulationServlet using Java 1.8.0_381 on ATSAAIPRDSTB1 with PID 6704 (started by ATSAAIPRDSTB1$
FINE  [SimulationServlet] Running with Spring Boot v2.7.18, Spring v5.3.31
INFO  [SimulationServlet] No active profile set, falling back to 1 default profile: "default"
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
INFO  [JawsRestApiCallerForSIM] login to JAWS server failed due to JAWS server initializing or incorrect credential, trying again
DEBUG [JawsRestApiCallerForSIM] Successfully updated JAWS server cookie.
DEBUG [SimulationConfiguration] testMode is: false
INFO  [SimulationService] Starting Simulation Service

Powered by Wolken Software