activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r864311 - in /websites/production/activemq/content: cache/main.pageCache virtual-destinations.html
Date Tue, 04 Jun 2013 05:24:56 GMT
Author: buildbot
Date: Tue Jun  4 05:24:56 2013
New Revision: 864311

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/virtual-destinations.html

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/virtual-destinations.html
==============================================================================
--- websites/production/activemq/content/virtual-destinations.html (original)
+++ websites/production/activemq/content/virtual-destinations.html Tue Jun  4 05:24:56 2013
@@ -225,7 +225,7 @@
 
 <h2><a shape="rect" name="VirtualDestinations-AvoidingDuplicateMessageinaNetworkofBrokers"></a>Avoiding
Duplicate Message in a Network of Brokers</h2>
 
-<p>You have to make sure that the messages sent to the <b>Consumer.*.VirtualTopic.&gt;</b>
destination are not forwarded.  If you use Virtual Topics in a network of brokers, it is likely
you will get duplicate messages if you use the default network configuration.  This is because
a network node will not only forward message sent to the virtual topic, but also the associated
physical queues.  To fix this, you should disable forwarding messages on the associated physical
queues.  </p>
+<p>You have to make sure that the messages sent to the <b>Consumer.*.VirtualTopic.&gt;</b>
destination are not forwarded when you're using both queue-based and non-queue based subscribers
to the virtual topic (that is, if you have normal topic subscribers to the virtual topic).
 If you use Virtual Topics in a network of brokers, it is likely you will get duplicate messages
if you use the default network configuration.  This is because a network node will not only
forward message sent to the virtual topic, but also the associated physical queues.  To fix
this, you should disable forwarding messages on the associated physical queues.  </p>
 
 <p>Here is an example of how to do that:</p>
 



Mime
View raw message