If the eserver drops a connection to the selfservice console the selfservice console does not attempt to reestablish a new connection
Originally Published: 2011-08-29
Article Number
Applies To
Issue
Whenever there is an interruption in the eserver connection to the self service console, the eserver does not attempt to establish a new connection
Cause
Resolution
This is a defect in the selfservice.war file, and is corrected in AxM hotfix 6.1.3.14 or higher. Do to a change in the way jar files are signed you must first be on hotfix 6.1.3.4 or higher to install hotfix 6.1.3.14.
To obtain this hotfix, please contact RSA AxM support, and request hotfix 6.1.3.14 (or the latest selfservice.war hotfix, as all hofixes for each component are cumulative)
Related Articles
Failed RSA SecurID Authenticate tokencode authentication attempt to RSA SecurID Authentication Manager causes two failures… Number of Views Test connector settings of an Active Directory LDAP AFX Connector configured to use SSL over port 636 fails with 'Failed c… Number of Views Active Directory AFX Connector Add Account to Group capability fails with 'No Such Attribute' error in RSA Identity Govern… Number of Views Error message "Illegal TXN State: Attempt to start new transaction during rollback" in RSA Identity Governance & Lifecycle Number of Views RSA Authentication Manager 8.1 and 8.2 show a system message that administrator "trustedapp" attempted to update a princip… Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
