Details

    • Type: Sub-task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.3.0.ER1
    • Component/s: Clustering
    • Labels:
      None
    • Environment:

      Windows and fedora

    • Release Notes 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 Notes Docs Status:
      Needs More Info
    • Docs QE Status:
      NEW

      Description

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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  baranowb Bartosz Baranowski
                  Reporter:
                  ShaunA Shaun Appleton
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  13 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: