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>
- incorporates
-
JBEAP-13175 Upgrade JBoss Remoting to 5.0.2.Final
- Closed
-
JBEAP-13176 Upgrade WildFly Naming Client to 1.0.3.Final
- Closed
- is blocked by
-
WFLY-9358 Remote EJB clustered node discovery is ignored
- Closed
- is caused by
-
EJBCLIENT-262 PROVIDER_URL failover/retry is not happening
- Resolved
-
JBEAP-12284 [GSS](7.1.0) User can not override with InitialContext properties as expected if wilfdfly-config-xml is used
- Closed
- is cloned by
-
WFLY-9358 Remote EJB clustered node discovery is ignored
- Closed
- is incorporated by
-
JBEAP-12603 Upgrade to http client 1.0.1.Final
- Closed
-
JBEAP-12888 Upgrade JBoss EJB Client to 4.0.1.Final
- Closed
-
JBEAP-13178 Upgrade WildFly HTTP client components to 1.0.3.Final
- Closed
- is related to
-
JBEAP-13224 SFSB session open requests don't retry if a node is down
- Closed
-
JBEAP-13191 DwmNeverTestCase assumes clustered invocations will always go to the same node
- Closed
- relates to
-
EJBCLIENT-195 Consider changes needed for handling multiple provider URLs
- Resolved
-
WFNC-39 Add primary support for multi-location providers
- Resolved
-
WFTC-32 Add support for multi-destination providers
- Resolved