activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r974427 - in /websites/production/activemq/content: cache/main.pageCache networks-of-brokers.html
Date Thu, 03 Dec 2015 18:21:24 GMT
Author: buildbot
Date: Thu Dec  3 18:21:24 2015
New Revision: 974427

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 Thu Dec  3 18:21:24 2015
@@ -176,7 +176,7 @@
       		<queue physicalName="always.include.queue"/>
         </staticallyIncludedDestinations>
 &lt;/networkConnector&gt;</pre>
-</div></div><p>If configured like this, broker will try to listen for new
consumers on <code>ActiveMQ.Advisory.Consumer.NO_DESTINATION</code>, which will
never have messages so it will be protected from information on remote broker consumers.</p><h3
id="NetworksofBrokers-DynamicnetworksandVirtualDestinations(Newfor5.13.0)">Dynamic networks
and Virtual Destinations (New for 5.13.0)</h3><p>As described above, a network
of brokers can be configured to only send messages to a remote broker when there's a consumer
on an included destination. &#160;However, let's consider some cases of how dynamic flow
occurs when&#160;<a shape="rect" href="virtual-destinations.html">Virtual Destinations</a>&#160;are
in use.</p><h4 id="NetworksofBrokers-VirtualDestinationconsumersandCompositeDestinations">Virtual
Destination consumers and Composite Destinations</h4><p>Here is an example of
two brokers networked together. &#160;The local broker contains the network connector
configured with a&#160;<code>dy
 namicallyIncludedDestination</code>&#160;and the remote broker is configured with
a CompositeTopic:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Local Broker</b></div><div
class="codeContent panelContent pdl">
+</div></div><p>If configured like this, broker will try to listen for new
consumers on <code>ActiveMQ.Advisory.Consumer.NO_DESTINATION</code>, which will
never have messages so it will be protected from information on remote broker consumers.</p><h3
id="NetworksofBrokers-virtualconsumersDynamicnetworksandVirtualDestinations(Newfor5.13.0)"><span
class="confluence-anchor-link" id="NetworksofBrokers-virtualconsumers"></span>Dynamic
networks and Virtual Destinations (New for 5.13.0)</h3><p>As described above,
a network of brokers can be configured to only send messages to a remote broker when there's
a consumer on an included destination. &#160;However, let's consider some cases of how
dynamic flow occurs when&#160;<a shape="rect" href="virtual-destinations.html">Virtual
Destinations</a>&#160;are in use.</p><h4 id="NetworksofBrokers-VirtualDestinationconsumersandCompositeDestinations">Virtual
Destination consumers and Composite Destinations</h4><p>Here is an example of
two brokers netwo
 rked together. &#160;The local broker contains the network connector configured with
a&#160;<code>dynamicallyIncludedDestination</code>&#160;and the remote
broker is configured with a CompositeTopic:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeHeader panelHeader pdl" style="border-bottom-width: 1px;"><b>Local
Broker</b></div><div class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">&lt;networkConnector
uri="static:(tcp://host)"&gt;
 	&lt;dynamicallyIncludedDestinations&gt;
     	&lt;topic physicalName="include.test.bar"/&gt;



Mime
View raw message