[
https://issues.apache.org/jira/browse/AMQ-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017147#comment-13017147
]
Scott Emmons commented on AMQ-2743:
-----------------------------------
We have seen this same thing. Everything was fine in 5.3.0, but unable to
failover to slave in 5.4.2. This is a serious issue - we cannot rollback to
5.3.0 due to other bugs, fixed in later versions - and we can not deploy a
fault-tolerant configuration on a newer version, because of this bug.
> Pure master/slave configuration will not failover to slave when master fails
> -----------------------------------------------------------------------------
>
> Key: AMQ-2743
> URL: https://issues.apache.org/jira/browse/AMQ-2743
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: Bruce Snyder
> Fix For: 5.6.0
>
> Attachments: activemq-brokerA.xml, activemq-brokerB-master.xml,
> activemq-brokerB-slave.xml
>
>
> When using a pure/master slave configuration in ActiveMQ 5.3.1 and the master
> is killed, the failover to the slave never takes place.
> Below is a description of the topology being used:
> * The producer sends messages to brokerA
> * BrokerA has a uni-directional network connection using the failover
> transport to brokerB-master and brokerB-slave
> * BrokerB-master and brokerB-slave each have a uni-directional network
> connection using failover to brokerA
> * The consumer uses a failover connection to brokerB-master and brokerB-slave
> Below are the steps to reproduce the problem:
> # In terminal one, start up brokerA
> # In terminal two, start up brokerB-master
> # In terminal three, start up brokerB-slave
> # In terminal four, start up the consumer that connects to brokerB-master and
> brokerB-slave
> # In terminal five, startup the producer that connects to brokerA to send
> messages
> # In terminal two, kill brokerB-master
> # Notice that the producer will continue sending messages until producer flow
> control kicks in and blocks the send operation, but brokerB-slave never takes
> over
> I copied the same exact configuration files over to instances of ActiveMQ
> 5.3.0 and it works without a problem. There must be something in ActiveMQ
> 5.3.1 that is causing this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
