[AMQ-2743] Pure master/slave configuration will not failover to slave when master fails

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.3.1
• Fix Version/s: 5.6.0
• Assignee: Unassigned
• Reporter: Bruce Snyder
• Created: 20/May/10 04:46
• Updated: 28/Oct/11 08:04
• Resolved: 28/Oct/11 08:04

Description

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:

1. In terminal one, start up brokerA
2. In terminal two, start up brokerB-master
3. In terminal three, start up brokerB-slave
4. In terminal four, start up the consumer that connects to brokerB-master and brokerB-slave
5. In terminal five, startup the producer that connects to brokerA to send messages
6. In terminal two, kill brokerB-master
7. 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.