EJBCLIENT000025: No EJB receiver available for handling error when loading Workflow Architect in RSA Identity Governance and Lifecycle
Originally Published: 2017-09-28
Last Modified: 2023-11-30
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 How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle Number of Views 'Could not deserialize result from HTTP invoker remote service' error when opening/editing workflows in RSA Identity Gover… 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
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x RSA Governance & Lifecycle 8.0.0 Installation Guide
Don't see what you're looking for?
