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 3.85KNumber of Views RSA Identity Governance & Lifecycle 7.0.2 Workflow hangs when loading with error "content must be served over HTTPS error" 142Number 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… 728Number of Views Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle 509Number of Views 'Could not deserialize result from HTTP invoker remote service' error when opening/editing workflows in RSA Identity Gover… 241Number of Views
Trending Articles
RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process Downloading RSA Authentication Manager license files or RSA Software token seed records When configuring LDAP or LDAPS in RSA Authentication Manager with a global catalog the connection fails
Don't see what you're looking for?