EJB Client will not failover as expected if an application is marked as a singleton-deployment in EAP 7

Solution Unverified - Updated -

Issue

  • If an application is marked as singleton-deployment in a cluster it is deployed active on one node only. If a client does not have this node for the initial context every invocation to an EJB will fail with EJBCLIENT000025 message. How can I ensure the application can be invoked?
  • If a singleton-deployment in a cluster should be used from an EJB-client the failover is not working as expected. If the node, which is working for invocation, goes down the client stop invocations and throw an EJBCLIENT000025 error.
  • SInce EAP7 it is possible to mark an application as singleton-deployment, if EJB's are deployed the ejb-client will only be able to invoke the EJB if the node with the active deployement is in the initial server list from the client. Neither another node is seen nor a failover will work. How I can enable full failover awareness?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content