activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Created) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Created] (AMQNET-380) FailoverTransport doesn't tigger a reconnect on send of a Tracked Command.
Date Fri, 13 Apr 2012 13:55:16 GMT
FailoverTransport doesn't tigger a reconnect on send of a Tracked Command.
--------------------------------------------------------------------------

                 Key: AMQNET-380
                 URL: https://issues.apache.org/jira/browse/AMQNET-380
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: ActiveMQ
    Affects Versions: 1.5.4, 1.5.3, 1.6.0
            Reporter: Timothy Bish
            Assignee: Timothy Bish
             Fix For: 1.5.5, 1.6.0


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. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message