activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r882741 - in /websites/production/activemq/content: cache/main.pageCache networks-of-brokers.html
Date Tue, 15 Oct 2013 15:28:31 GMT
Author: buildbot
Date: Tue Oct 15 15:28:31 2013
New Revision: 882741

Production update by buildbot for activemq


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

Modified: websites/production/activemq/content/networks-of-brokers.html
--- websites/production/activemq/content/networks-of-brokers.html (original)
+++ websites/production/activemq/content/networks-of-brokers.html Tue Oct 15 15:28:31 2013
@@ -32,16 +32,6 @@
-          <link href=''
rel='stylesheet' type='text/css' /> 
-      <link href=''
rel='stylesheet' type='text/css' /> 
-      <script src='' type='text/javascript'></script>

-              <script src=''
-              <script src=''
-      <script type="text/javascript"> 
-        SyntaxHighlighter.defaults['toolbar'] = false; 
-        SyntaxHighlighter.all(); 
-      </script> 
     Apache ActiveMQ &#8482; -- Networks of Brokers
@@ -216,6 +206,9 @@ When disabling this feature such network
 However networks cannot add durability when the source is non durable. Non durable topic
subscriptions and temporary destinations (both queues and topics) are non durable by definition.
When non durable<br clear="none">
 sources are networked, in the event of a failure, inflight messages can be lost.</p>
+<h4><a shape="rect" name="NetworksofBrokers-Ordering"></a>Ordering</h4>
+<p>Total message ordering is not preserved with networks of brokers. Total ordering
<a shape="rect" href="how-do-i-preserve-order-of-messages.html" title="How do I preserve
order of messages">works with a single consumer</a> but a networkBridge introduces
a second consumer. In addition, network bridge consumers forward messages via producer.send(..),
so they go from the head of the queue on the forwarding broker to the tail of the queue on
the target. If single consumer moves between networked brokers, total order may be preserved
if all messages always follow the consumer but this can be difficult to guarantee with large
message backlogs.</p>
 <h4><a shape="rect" name="NetworksofBrokers-WhentouseandnotuseConduitsubscriptions"></a>When
to use and not use Conduit subscriptions</h4>
 <p>ActiveMQ relies on information about active consumers (subscriptions) to pass messages
around the network. A broker interprets a subscription from a remote (networked) broker in
the same way as it would a subscription from a local client connection and routes a copy of
any relevant message to each subscription. With Topic subscriptions and with more than one
remote subscription, a remote broker would interpret each message copy as valid, so when it
in turns routes the messages to its own local connections, duplicates would occur. Hence default
conduit behavior consolidates all matching subscription information to prevent duplicates
flowing around the network. With this default behaviour, N subscriptions on a remote broker
look like a single subscription to the networked broker.</p>

View raw message