AMQ 5.4
<amq:networkConnectors>
<amq:networkConnector
uri="static:(tcp://the.other.broker)"
conduitSubscriptions="true" duplex="false"
dynamicOnly="false"
suppressDuplicateQueueSubscriptions="true"
suppressDuplicateTopicSubscriptions="true"
decreaseNetworkConsumerPriority="false">
<amq:excludedDestinations>
<amq:queue physicalName="Consumer.*.VirtualTopic.>"/>
</amq:excludedDestinations>
</amq:networkConnector>
</amq:networkConnectors>
1. Network of 2 brokers, B1 and B2
2. Single consumer C, connected via failover protocol to B1
*3. Message sent to VirtualTopic VT on B1*
4. Message received by C via Consumer.C.VT queue on B1, nothing left in the
queue B1
*5. Message duplicated in Consumer.C.VT queue on B2
6. Reconnect consumer to B2 - duplicate messages delivered from B2*
similarly
*3. Message sent to VirtualTopic VT on B2*
4. Message received by C via Consumer.C.VT queue on B1, nothing left in the
queue B1
*5. Message duplicated in Consumer.C.VT queue on B2
6. Reconnect consumer to B2 - duplicate messages delivered from B2*
conclusion
- Messages get removed only from the physical queue the consumer is
currently connected to
- Messages pile up in the queue on the broker the consumer is not currently
connected to
is this expected? I can set message expiry, but it would still be in hours,
which would introduce crazy amount of duplication.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NetworkOfBrokers-VirtualTopic-duplicates-tp4079456p4079456.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
