Author: buildbot
Date: Wed May 1 20:21:35 2013
New Revision: 860519
Log:
Production update by buildbot for activemq
Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/networks-of-brokers.html
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 Wed May 1
20:21:35 2013
@@ -199,6 +199,12 @@ When disabling this feature such network
</div>
+
+<h4><a shape="rect" name="NetworksofBrokers-Reliability"></a>Reliability</h4>
+<p>Networks of brokers do reliable store and forward of messages. If the
source is durable, persistent messages on a queue or a durable topic
subscription, a network will retain the durability guarantee. <br clear="none">
+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-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>
