ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AAI Failed to allow logins to secondary EEM server while primary EEM server was down for patching

book

Article ID: 213409

calendar_today

Updated On:

Products

Automic Automation Intelligence

Issue/Introduction

AAI Failed to allow logins to secondary EEM server while primary EEM server was down for patching.

 

You may see a timeout message like below when this occurs:

INFO [EIAMLoginImpl] login failed: com.termalabs.common.JawsException: Couldn't connect (tried for 15 seconds)
    at com.termalabs.server.security.EIAMLoginImpl.checkCredentials(EIAMLoginImpl.java:87)
    at com.termalabs.server.ejb3.security.JawsLoginModule2.login(JawsLoginModule2.java:139)
    ... 52 skipped

This can also cause the "jaws.sh stopsync" command to become unresponsive and require you to kill the jboss process in order to restart services and recover from this issue.

Cause

Defect DE471590

Environment

Release : 6.0

Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE

Resolution

There is a new server parameter added in 6.2.0-2 in the AAI configuration tool called,  eEM.connectionTimeout (default = 30 seconds) parameter that may need to be modified depending on your environment.

This timeout will allow AAI a longer or shorter amount of time to attempt to connect to secondary EEM servers for authentication.

https://docs.automic.com/documentation/webhelp/english/ALL/components/TERMA/latest/AAI%20Guides/Content/AAI_Topics/Release_Notes_6_2_0/BugFixes_6_2_0.htm