-
Bug
-
Resolution: Done
-
Major
-
4.0.14.Final
-
None
NamingEJBClientInterceptor allows discovering destinations for invocations based on the list of URLs in the JNDI InitialContext variable PROVIDER_URL. If the invocation has a proxy with (strong affinity, weak affinity) = (NONE, NONE), this interceptor will be used to choose a destination over DiscoveryEJBClientInterceptor.
Like DiscoveryEJBClientInterceptor, NamingEJBClientInterceptor calls DiscoveryEJBClientInterceptor.setupSessionAffinities() to adjust affinity values in specific cases. However, whereas DiscoveryEJBClientInterceptor does this after the invocation has returned, NamingEJBClientInterceptor does it before the invocation goes out. This means that any changes to affinity made on the server are not so processed.
- blocks
-
WFLY-11489 SFSB not sticky on a single cluster node when clustering of the bean is disabled
- Closed
- is cloned by
-
JBEAP-16390 [GSS](7.2.z) EJBCLIENT-319 - Update affinities on return in NamingEJBClientInterceptor
- Closed
- is related to
-
WFLY-11489 SFSB not sticky on a single cluster node when clustering of the bean is disabled
- Closed