EJBCLIENT000025: No EJB receiver available for handling error when loading Workflow Architect in RSA Identity Governance and Lifecycle
Originally Published: 2017-09-28
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2
Platform: WildFly Cluster
Issue
EJBCLIENT000025: No EJB receiver available for handling [appName:aveksa, moduleName:wpServer, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@a5a2d6e We have a clustered enterprise environment.Cause
Resolution
NOTE: Make sure all cluster nodes are started, undeploy the WFArchitect.ear, redeploy the ear, shutdown the host controllers, restart the domain controller and restart each host controller.
Related Articles
Artifacts to gather in RSA Identity Governance & Lifecycle Number of Views RSA Identity Governance & Lifecycle 7.0.2 Workflow hangs when loading with error "content must be served over HTTPS error" Number of Views Workflow shows 'Workflow flagged as stalled based on stall detection settings' error in versions 6.9.1 and 7.0 of RSA Ide… Number of Views How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Number of Views Getting 'Request Error : The request could not be handled' error when trying to access requests in RSA Identity Governance… Number of Views
Trending Articles
Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update Authentication Manager How to Retrieve the LDAPS Certificate and Configure an External Identity Source to Use LDAPS
Don't see what you're looking for?
