Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 28 Feb 2012 20:19:46 +0000 (UTC)
From: "Mirko Golze (Updated) (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <1973099782.30090.1330460386562.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <197009136.27214.1330418868730.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (AMQ-3744) FailoverTransport connects to inactive
 slave Broker
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mirko Golze updated AMQ-3744:
-----------------------------

    Attachment:     (was: activemq.test.zip)
    
> FailoverTransport connects to inactive slave Broker
> ---------------------------------------------------
>
>                 Key: AMQ-3744
>                 URL: https://issues.apache.org/jira/browse/AMQ-3744
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.5.1
>         Environment: Windows 7 x64, Java 1.6_30
>            Reporter: Mirko Golze
>
> The bug affects the ActiveMQ-Fuse Version 5.5.1-fuse-02-02. The version 5.5.1-fuse-00-08 is the last testet with no problem.
> when trying to connect to a failover-url with multiple failover nodes, the failover transport connects successful already at the first node, even if it is an inactive slave. 
> Then, of course, no session can be started. The consumer is waiting all the time.

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