I have been using ActiveMQ-5.4.2 in a stoke and hub configuration for some time now. I have successfully used a full duplex network connector between the hub and each spoke. Queues in the spokes that match queues in the hub are connected and messages flow between the queues automatically.
I just started testing ActiveMQ-5.7.0 as a possible replacement for the hub (The spoke is still 5.4.2). I set up a full duplex connection to a spoke and started both brokers. It appears that the queue that routes data from the hub to the spoke is working, but the queue that routes data from the spoke back to the hub (different queue) is not working. The Network Bridges status under the Network tab in the browser correctly shows that each end of the network bridge has been set up correctly. However, on the Queue page for the queue that is sending information back to the hub clearly shows that there is no consumer. If I had to guess, I would say there is something wrong with the Advisory Messages that tells the hub about the spoke's queue or the other way around. Any ideas? Has anyone figured out what is causing this problem? -- View this message in context: http://activemq.2283324.n4.nabble.com/Queues-not-connected-together-at-each-end-of-a-Full-Duplex-NetworkConnector-tp4662085.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
