EJB invocations for deployed applications using remote-interface will not stay local for EAP 7.2 server

Solution Verified - Updated -


  • EAP 6 and 7.0 will keep EJB invocations bound to the local node even if the remote interface is used as long as the EJB is deployed local and it is not excluded within the jboss-ejb-client.xml
  • Invocation of a remote EJB are using instances in a cluster in a random manner after we migrate from 7.0 to 7.2, for legacy versions it was keept in the same instance
  • If an application is deployed inside of EAP (7.0) which invoke another EJB via remote interface the invocation will use always the local deployed application (if available) by default. After migration to EAP 7.2 the invocation will be random to instances where the application is available. This is unexpected as the jboss-ejb-client.xml only allows to exclude the local-receiver but the local invocation is faster as we have configured the invocation by reference.


  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.1 ... 7.2.3

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