Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 29 Sep 2011 21:43:45 +0000 (UTC)
From: "Timothy Bish (Resolved) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1886896133.9251.1317332625885.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1670290983.5101.1317240285435.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (AMQ-3517) Failover Transport will never call
 transportResumed when it reconnects to a hot backup transport.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMQ-3517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-3517.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 5.6.0

Fixed in trunk, new tests added for the backups option.
                
> Failover Transport will never call transportResumed when it reconnects to a hot backup transport.
> -------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3517
>                 URL: https://issues.apache.org/jira/browse/AMQ-3517
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.x
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 5.6.0
>
>
> The Failover transport will always call transportInterrupted but if there's a hot backup in the backups list it won't call the transportResumed method on its listener, it just reconnects and returns.

--
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