Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-115

EJBClientContext is left in broken state if there are no reconnection handlers + broken synchronization.

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 2.1.0.Final
    • Fix Version/s: 2.1.0.Final
    • Labels:
      None

      Description

      If "attemptReconnections" method of the EJBClientContext is called when there are no reconnection handlers available (it's quite common situation) the component is being left in the "attemptingReconnect" state forever so no reconnection is possible even if new reconnection handlers will become available later.

      The second problem is that the array of reconnection handlers is not properly synchronized when it's copied to the new array.

      Pull request available.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dmlloyd David Lloyd
                Reporter:
                slawomir.wojtasiak SÅ‚awomir Wojtasiak
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: