Some further information: In the DemandForwardBridgeSupport, temporary destinations are not processed as part of the "excludedDestinations' config. Therefore, in the above set of networkConnectors, temporary destinations are processed for BOTH connectors instead of just the one for topics.
We can prove this by taking away the core1_queues connector. When we do that, there are no more duplicates. So the real problem is that temp destinations are being bridged multiple times per broker-to-broker connection. So question: Why are temp destinations not part of the "excludedDestinations" logic on the forwarding bridge? Question 2: Is the right fix to add temp-destinations to the logic, or maybe a new config to allow temp-destinations in the excludes? -- View this message in context: http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3210043.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
