Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-17344

[GSS](7.2.z) EJBCLIENT-343 - EJB invocation will not stay local if the application is deployed local and the Remote interface is used

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.2.6.CR1, 7.2.6.GA
    • 7.2.0.GA
    • EJB
    • 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

              rhn-support-wfink Wolf Fink
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: