Wait, there are multiple transport connections between A and B? Why? That right there seems like a problem, and might be the root cause of the behavior you're seeing.
The code I see in that processBrokerInfo() method creates the inverse side of the duplex network connection (under the hood it's not a single two-way connection, but rather two one-way connections), but I don't see anything that seems concerning about what it's doing. Tim On Mon, Jul 31, 2017 at 8:10 AM, tpavelka <tomas.pave...@ca.com> wrote: > I got a little further today: > The reason that conduit does not happen is that even though ConsumerInfos > come twice for the same topic, they come over different transport > connections and thus come to different bridges. For conduit to happen it > must happen within one bridge. > Also, I noticed that when A,C and D (spokes) connect to B (hub) they do so > over duplex connections. I noticed some special processing for duplex > connections, namely that it creates additional bridges, in > org.apache.activemq.broker.TransportConnection#processBrokerInfo. > > Tomas > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Duplicate-messages-received-with-ActiveMQ-5-13-2- > tp4728627p4729068.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
