You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mirko Golze (Created) (JIRA)" <ji...@apache.org> on 2012/02/28 09:47:48 UTC
[jira] [Created] (AMQ-3744) FailoverTransport connects to inactive
slave Broker
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
[jira] [Resolved] (AMQ-3744) FailoverTransport connects to inactive
slave Broker
Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3744.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Tested against latest 5.6 SNAPSHOT and the test case passes without error.
> 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
> Fix For: 5.6.0
>
> 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
[jira] [Commented] (AMQ-3744) FailoverTransport connects to
inactive slave Broker
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQ-3744) FailoverTransport connects to inactive
slave Broker
Posted by "Mirko Golze (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQ-3744) FailoverTransport connects to inactive
slave Broker
Posted by "Mirko Golze (Updated) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (AMQ-3744) FailoverTransport connects to inactive
slave Broker
Posted by "Mirko Golze (Updated) (JIRA)" <ji...@apache.org>.
[ 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
activemq.test.zip contains an unit test which demonstrates the maloperation
> 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