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
I1912 - The SEL is full of events and is unable to log any more Number of Views 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 Database Statistics running after every collection in RSA Identity Governance & Lifecycle Number of Views java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got NCLOB in RSA Identity Governance & Lif… Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
