In and environment with eEM failover configured, eEM users sometimes cannot login to AAI when primary eEM server is down.
They will attempt to login and it will take a long time for the login to eventually fail.
Release : 6.2.0
Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE
Upgrade to at least 6.4.1 which introduced several new parameters, which should prevent AAI from trying to connect to the primary eEM server for longer then 30 seconds by default before attempting a secondary eEM server..
The 3 new server parameters introduced int 6.4.1 are:
To turn on eem logs "eem.network.java.log" and "eem.sdk.java.log" update eem.log4j.xml by updating the "level value" to TRACE for Network and SDK.
<!-- valid levels are: ALL < TRACE < DEBUG < INFO < WARN < ERROR < FATAL < OFF-->
<logger name='Network' additivity='false'>
<level value='TRACE'/>
<appender-ref ref='Network' />
</logger>
<root>
<level value='TRACE'/>
<appender-ref ref='SDK' />
</root>
</log4j:configuration>
Existing server parameters usage:
eEM.socketTimeout: the time to wait for a packet to be received.