[QPID-8142] Federated Bindings Do not properly propagate in Line or Star Topology When Brokers are not directly connected to each other

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: qpid-cpp-1.37.0
• Component/s: C++ Broker

Environment

CentOS Linux release 7.4.1708 (Core)

Linux db515b3a4663 4.9.58-18.55.amzn1.x86_64 #1 SMP Thu Nov 2 04:38:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Qpid cpp broker 1.37.0
Qpid cpp client 
Qpid tools           (qpid-route, qpid-config, qpid-tool)

• Assignee: Unassigned
• Reporter: Tom Peterson
• Created: 28/Mar/18 03:08
• Updated: 28/Mar/18 03:08

Description

1. Start 3 brokers broker1, broker2, and broker3
2. Connect subscriber to TEST/a.b.c to broker3
3. Setup durable dynamic federated routes in line topology
    broker2 <=> broker1 <=> broker3

1. Publish message on TEST/a.b.c via broker2
2. Verify message received by subscriber connected broker
3.  This works as expected to this point

1.  Stop broker2 (publisher broker)
2.   Restart broker2 (publisher broker)
3.   Sleep 5 seconds to make sure there is time for federated links to recover
4.   Verify routes  – qpid-route route map localhost:44441   (broker1)
5.  Publish message on TEST/a.b.c via broker2
6.   Message is NOT received by subscriber connected to broker3

Run attached test script testRestartPropagation.sh to reproduce the flow above and the failure.

Run testStartupPropagation.sh to test only to step 5.    This will allow inspection of the broker bindings before broker2 is restarted.   If the broker bindings are compared at step 5 and step 12 you will seed that broker2 loses a binding to the broker1 bridge queue for TEST/a.b.c