-
Bug
-
Resolution: Done
-
Major
-
7.2.0.GA
-
None
If an application is deployed and try to call a different EJB via remote interface the proxy will use all possible endpoints randomly no matter whether the application is deployed local or not.
This is a regression when migrating from EAP 7.0->7.1+ because of the new implementation.
— 7.0 ----
There was a server side implementation
org.jboss.as.ejb3.remote.LocalEJBReceiverPreferringDeploymentNodeSelector
which ensure the local node name is returned if available for selection.
— 7.1+ —
The ejb-client implementation will use interface defaults and static references to provide several different implementations and here the RANDOM implementation is used and there is no one to prefer a local deployment
- clones
-
EJBCLIENT-343 EJB invocation will not stay local if the application is deployed in a local serer and the Remote interface is used
- Resolved
- is incorporated by
-
JBEAP-17666 [GSS](7.2.z) Upgrade jboss-ejb-client from 4.0.23.Final-redhat-00001 to 4.0.27.Final
- Closed
- links to