Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-1771

Failover transport should always signal resume of transport

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 5.1.0
    • 5.2.0
    • Transport
    • None
    • WinXP, JDK5

    • Patch Available

    Description

      The FailoverTransport does currently not signal the initial resume of the transport (due to race condition) nor the failure (if maxReconnectAttempts is 0) and therefore we don't know if the connection is successfully connected or not.

      The attached patch adds a sleep (copied from the failure processing part some lines below) that ensures that the transportListener is set and the transportListener.transportResumed() is called.

      Attachments

        1. amq-failover-reconnect.patch
          1 kB
          Andreas Kuhtz
        2. ASF.LICENSE.NOT.GRANTED--amq-failover.patch
          2 kB
          Andreas Kuhtz

        Activity

          People

            rajdavies Robert Davies
            akuhtz Andreas Kuhtz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: