activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Updated] (AMQ-2743) Pure master/slave configuration will not failover to slave when master fails
Date Fri, 01 Apr 2011 11:22:10 GMT


Gary Tully updated AMQ-2743:

    Fix Version/s:     (was: 5.5.0)

> Pure master/slave configuration will not failover to slave when master fails 
> -----------------------------------------------------------------------------
>                 Key: AMQ-2743
>                 URL:
>             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:

View raw message