Sorry, I was so focused on the difference between the enqueue and dequeue counts that I missed that row in your earlier post.
So that confirms that despite using a DurableConduitBridge, the subscriptions are not actually being combined, which is indeed what I was asking. (And yes, your understanding of what happens when subscriptions are conduited is exactly right.) The only way that brokers know to forward messages across a dynamically included networkConnector is by getting messages on the appropriate advisory topic for a given destination. I've never looked at what type those messages have, but ConsumerInfo sounds plausible. But if you see the consumer count increasing without hitting your breakpoint, then that doesn't match my mental model of how the network bridges work. I probably won't have time to go through the code before the weekend, but if you don't have it figured out by then, I can see if I can pinpoint where you'd want to set your breakpoint to catch the decision about whether to conduit or not. Tim On Jul 27, 2017 7:37 AM, "tpavelka" <tomas.pave...@ca.com> wrote: > The tables I sent before have a row named "Number of consumers". These are > from org.apache.activemq.broker.jmx.DestinationViewMBean#getConsumerCount > > I also put a breakpoint in org.apache.activemq.broker. > region.Topic#dispatch > And logged the number of consumers > (org.apache.activemq.broker.region.Topic#consumers.length()), on every > broker (including A) it was always 2 (of type > org.apache.activemq.broker.region.TopicSubscription). > > Is this what you mean when you say "we have two subscriptions on A"? > > Also, can you confirm that my understanding of conduitSubscriptions is > correct? > The way I understand it is that if there is a broker (X) who sends a > message > to another broker (Y) that has multiple subscriptions for it then X tracks > it as just one subscription so that it does not have to send the message > multiple times. > > I am trying to debug where exactly does the decision not to conduit get > made > but I am still kind of lost in the code. > > Tomas > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2- > tp4728627p4728962.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
