[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 updated WFLY-9358:
-------------------------------
    Description: Due to issues with affinity processing, authentication stickiness, and user transaction stickiness, node topology information is effectively ignored, causing balancing and failover to not behave properly.  (was: 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>)


> 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: Jason Greene
>            Priority: Blocker
>
> Due to issues with affinity processing, authentication stickiness, and user transaction stickiness, node topology information is effectively ignored, causing balancing and failover to not behave properly.



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