[AMQ-3798] Network connector does not establish connections to a slave broker after master failure

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.6.0
• Component/s: Broker
• Assignee: Unassigned
• Reporter: Hanno Wiegard
• Created: 03/Apr/12 11:02
• Updated: 13/Mar/22 14:08
• Resolved: 13/Mar/22 14:08

Description

We have a broker A which is connected to a master/slave pair (M/S) using a network connector with a static:failover configuration. A producer P writes to boker A and a consumer C consumes from brokers M/S. After M fails S becomes active but the no data flows from P to C anymore. Data seems to be stuck on A.

The master/slave pair is a normal ActiveMQ installation (attached config files master.xml and slave.xml). Broker A is started within a java process which runs in the TestProducer.java code, TestConsumer.java consumes messages from the master/slave pair.

Attached testcase shows the same behaviour.

Issue Links

• relates to: AMQ-5411 Rewrite static: transport to let it respond to reconnections by failover: transports within it
• relates to: AMQ-5412 Failover transport: disconnect existing connection when priorityBackup=true and priority broker becomes available, if maxReconnectAttempts=0