Note, when I patch DemandForwardingBridge to setNetworkConnection(true) on all BrokerInfo commands received by serviceRemoteCommand and patch TransportConnection to not create MasterBroker filters for networked slaves, this problem does not occur and things proceed as expected.
I think this should be filed as a bug but would like some advice to that effect first. -- View this message in context: http://activemq.2283324.n4.nabble.com/in-master-slave-broker-network-networked-slave-incorrectly-bound-to-other-slave-tp4658858p4658864.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
