[jboss-jira] [JBoss JIRA] (WFLY-9358) Remote EJB clustered node discovery is ignored

[Jason Greene (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene moved JBEAP-13186 to WFLY-9358:
--------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-9358  (was: JBEAP-13186)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: EJB
                       Naming
                       Remoting
                           (was: EJB)
                           (was: Naming)
                           (was: Remoting)
    Affects Version/s:     (was: 7.1.0.CR1)


> Remote EJB clustered node discovery is ignored
> ----------------------------------------------
>
>                 Key: WFLY-9358
>                 URL: https://issues.jboss.org/browse/WFLY-9358
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Naming, Remoting
>         Environment: 7.1.0.Beta and 7.1.0.ER2
>            Reporter: Wolf-Dieter Fink
>            Assignee: David Lloyd
>            Priority: Blocker
>
> If a client use PROVIDER_URL as property for InitialContext it is expected that if one of the servers is available the invocation is successful.
> But if the first server is not available the invocation fail as the provided proxy has an URI affinity even if there are multiple servers listed
>    Context.PROVIDER_URL == "http-remoting://localhost:8080,http-remoting://localhost:8180"
> The proxy looks like this:
> Proxy for remote EJB StatelessEJBLocator for "EAP71-PLAYGROUND-server/ejb/SimpleBean", view is interface org.jboss.wfink.eap71.playground.Simple, affinity is URI<http-remoting://localhost:8080>



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)