I'm having some trouble linking two brokers together using the documentation in section 1.4 (Broker Federation), and was looking for some advice.
* I currently have two brokers (192.168.1.1, 192.168.1.2) which use PLAIN SASL, and have appropriate ACL files allowing a user "test" access to everything once authenticated. * I then have two previously existing (not sure if this is where the problem starts, very little guiding debug information is printed) durable fanout topics on each broker called `test.fanout` -- this is the "initial" unfederated state. * At this point I run the following command on 192.168.1.2, in order to dynamically federate the `test.fanout` exchange to the "leader": > qpid-route -v dynamic add test/[email protected]:5672 test/password@localhost:5672 test.fanout Link state is Operational Creating inter-broker binding... Bridge method returned: 0 OK * Cool, seems like everything worked. However, on the other side my qpidd log file has the following: 2016-01-06 09:50:58 [Management] error Detected two management objects with the same identifier: 0-3-1--653(org.apache.qpid.broker:session:[email protected]_session_qpid.tcp :localhost:5672!test.fanout!test.fanout!_25c065aa-5b1b-465a-a6d2-510666f89248) which seems problematic, however the link is operational and there are no other errors. * Now I try to use the fanout by connecting to the local broker on 192.168.1.2 and sending some data. The data is indeed sent to the local fanout and I'm able to pick up those messages, but nothing is sent to the federated broker. Any hints as to where I'm going wrong here would be much appreciated! Matt
