Uploaded image for project: 'ActiveMQ .Net'
  1. ActiveMQ .Net
  2. AMQNET-380

FailoverTransport doesn't tigger a reconnect on send of a Tracked Command.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.5.3, 1.5.4, 1.6.0
    • 1.5.5, 1.6.0
    • ActiveMQ
    • None

    Description

      During a Oneway call to the FailoverTransport if the Command is tracked by the StateTracker the Failover Transport doesn't issue a call to handleTransportFailure resulting in a delay in starting a reconnect cycle. This can also have a negative impact on the ensureConnectionInfoSent in Connection if the WireFormat negotiator doesn't get its response to the WireFormatInfo request as it doesn't trigger an error on the request for ConnectionInfo response.

      Attachments

        Activity

          People

            tabish Timothy A. Bish
            tabish Timothy A. Bish
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: