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 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 RSA Identity Governance & Lifecycle 7.0.2 Workflow hangs when loading with error "content must be served over HTTPS error" Number of Views AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… Number of Views 'Could not deserialize result from HTTP invoker remote service' error when opening/editing workflows in RSA Identity Gover… 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 MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process
Don't see what you're looking for?
