Loading...

XML

Word

Printable

Release Note Text:

Hide
An issue with EJB3 load-balancing not updating a client's node list after a cluster node disconnects has been resolved in this release or EAP 5.

It was found that using the call-by-value attribute, with isolation as a property was causing FamilyClusterInfo to be overwritten by a JNDI call that triggers demarshaling of the MVP.

A 'finally' block has been added to the code to ensure the FamilyClusterInfo object is not overwritten once updated with new topology.

Show
An issue with EJB3 load-balancing not updating a client's node list after a cluster node disconnects has been resolved in this release or EAP 5. It was found that using the call-by-value attribute, with isolation as a property was causing FamilyClusterInfo to be overwritten by a JNDI call that triggers demarshaling of the MVP. A 'finally' block has been added to the code to ensure the FamilyClusterInfo object is not overwritten once updated with new topology.
Release Note Status:
Needs More Info
Docs QE Status:
NEW
Target Release:

EAP_EWP 5.3.0.GA

EJB3 load balancing doesn't keep client's node list up to date when call-by-value and isolation are used

is blocked by

EJBTHREE-2295 Fix wrong initialization of cluster members register