[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Updated] (AMQ-3744) FailoverTransport connects to inactive slave Broker
From:       "Mirko Golze (Updated) (JIRA)" <jira () apache ! org>
Date:       2012-02-28 20:23:46
Message-ID: 974690706.30113.1330460626416.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


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

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

    Attachment: activemq.test.zip

I added the fusesource repositoy to the pom.xml. So it should work.
The test fails with ActiveMQ 5.5.1-fuse-02-02 and runs successful with \
5.5.1-fuse-00-08  
> 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
> Attachments: activemq.test.zip
> 
> 
> 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

        


[prev in list] [next in list] [prev in thread] [next in thread]