You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org> on 2012/02/28 17:31:46 UTC

[jira] [Commented] (AMQ-3744) FailoverTransport connects to inactive slave Broker

    [ https://issues.apache.org/jira/browse/AMQ-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13218326#comment-13218326 ] 

Timothy Bish commented on AMQ-3744:
-----------------------------------

Tried to run your test, gives an error: "Could not resolve dependencies for project de.mgo:activemq.test:jar:0.0.1-SNAPSHOT:"
                
> 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