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 'Could not deserialize result from HTTP invoker remote service' error when opening/editing workflows in RSA Identity Gover… Number of Views AFX Server stuck in 'Not running' State, with error 'timed out waiting for AFX applications to start' Number of Views Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
Downloading RSA Authentication Manager license files or RSA Software token seed records RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory Mandatory Certificate Upgrade Required by 6th October 2025 for RSA MFA Agent for PAM, RSA MFA Agent for Apache, and Third … RSA Authentication Manager 8.9 Release Notes (January 2026)
Don't see what you're looking for?
