LB policies can now be aware of the node on which they
have been created by extending the new
LoadBalancePolicyEx interface. The FirstAvailable policy
has been modified to benefit from that feature.
In the past, proxies that had to pick-up a first target
couldn't simply ask on which node they had been
created and use that node. This is now possible.
This is specifically interesting for SFSB: the default
remote LB is now not only using the "FirstAvailable" (i.e.
sticky) policy but will also start using the node on which
the session has been originally created to perform
remote calls (i.e. the node on which the home.create
(...) has been performed.)
This is interesting for (possibly clustered) webapps
making calls to a remote and distinct cluster of SFSB
(http session containing a SFSB for example) as the
resulting load-balancing of SFSB may not be very
efficient in some cases and cause un-necessary failover
just after the session has been created.
The new behaviour should only be better (better
dispatching of session and less unnecessary initial
failovers). However, if you want to disable that new
the "jboss.cluster.proxy.dont_remember_home" Java
system property to "true" on the **client side** JVM.