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 Error message "Illegal TXN State: Attempt to start new transaction during rollback" in RSA Identity Governance & Lifecycle Number of Views RSA Via Lifecycle and Governance Workflow fails with error "Illegal TXN State: Attempt to start new transaction during rol… Number of Views Attempts to scrub/hash JSON data elements are not always working in RSA Web Threat Detection Number of Views RSA Identity Governance & Lifecycle Attribute Change Rule for Managed Attributes with argument "Set to old value of" does … Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) Artifacts to gather in RSA Identity Governance & Lifecycle RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
