activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1008383 - in /websites/production/activemq/content: cache/main.pageCache message-groups.html
Date Wed, 15 Mar 2017 15:23:10 GMT
Author: buildbot
Date: Wed Mar 15 15:23:09 2017
New Revision: 1008383

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/message-groups.html

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

Modified: websites/production/activemq/content/message-groups.html
==============================================================================
--- websites/production/activemq/content/message-groups.html (original)
+++ websites/production/activemq/content/message-groups.html Wed Mar 15 15:23:09 2017
@@ -110,7 +110,7 @@ if (message.getBooleanProperty("JMSXGrou
    // flush cache for groupId
 }
 </pre>
-</div></div><p>To flush caches to ensure consistent state when faced with
network errors.</p><h3 id="MessageGroups-AddingNewConsumers">Adding New Consumers</h3><p>If
you have existing messages in the broker and add consumers at a later stage, it is a good
idea to delay message dispatch start until all consumers are present (or at least to give
enough time for them to subscribe). If you don't do that the first consumer will probably
acquire all message groups and all messages will be dispatched to it. You can achieve this
by using <strong><code>consumersBeforeDispatchStarts</code></strong>
and <strong><code>timeBeforeDispatchStarts</code></strong> <a shape="rect"
href="per-destination-policies.html">destination policies</a>.</p><p>Here's
the example of the destination policy that delays dispatch for&#160;<strong><code>200ms</code></strong>:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+</div></div><p>To flush caches to ensure consistent state when faced with
network errors.</p><h3 id="MessageGroups-AddingNewConsumers">Adding New Consumers</h3><p>If
you have existing messages in the broker and add consumers at a later stage, it is a good
idea to delay message dispatch start until all consumers are present (or at least to give
enough time for them to subscribe). If you don't do that the first consumer will probably
acquire all message groups and all messages will be dispatched to it. You can achieve this
by using <strong><code>consumersBeforeDispatchStarts</code></strong>
and <strong><code>timeBeforeDispatchStarts</code></strong> <a shape="rect"
href="per-destination-policies.html">destination policies</a>.</p><p>When
both <strong>consumersBeforeDispatchStarts</strong> and <strong>timeBeforeDispatchStarts</strong>
are set to a value greater than zero, the dispatching will start as soon as the required number
of consumers are present or the timeBeforeDispatchStarts t
 imeout expires. If only consumersBeforeDispatchStarts is set then the timeout for consumers
to connect is 1 second. If all consumers disconnect then message dispatch delay will be applied
again at the next consumer connection.</p><p>&#160;</p><p>Here's
the example of the destination policy that delays dispatch for&#160;<strong><code>200ms</code></strong>:</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">&lt;destinationPolicy&gt;
   &lt;policyMap&gt;
     &lt;policyEntries&gt;
@@ -128,7 +128,7 @@ if (message.getBooleanProperty("JMSXGrou
   &lt;/policyMap&gt;
 &lt;/destinationPolicy&gt;
 </pre>
-</div></div><p>As <a shape="rect" class="external-link" href="http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/usecases/MessageGroupDelayedTest.java?view=markup">the
appropriate test case</a> shows, adding a small time pause before dispatching or setting
a minimum consumer number, ensures equal message group distribution.</p><div class="confluence-information-macro
confluence-information-macro-note"><p class="title">Availability</p><span
class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Available since version 5.3</p></div></div><h3
id="MessageGroups-See">See</h3><ul><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.html">How
do Message Groups compare to Selectors</a></li></ul></div>
+</div></div><p>As <a shape="rect" class="external-link" href="https://github.com/apache/activemq/blob/master/activemq-unit-tests/src/test/java/org/apache/activemq/usecases/MessageGroupDelayedTest.java"
rel="nofollow">the appropriate test case</a> shows, adding a small time pause before
dispatching or setting a minimum consumer number, ensures equal message group distribution.</p><div
class="confluence-information-macro confluence-information-macro-note"><p class="title">Availability</p><span
class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span><div
class="confluence-information-macro-body"><p>Available since version 5.3</p></div></div><h3
id="MessageGroups-See">See</h3><ul><li><a shape="rect" href="how-do-message-groups-compare-to-selectors.html">How
do Message Groups compare to Selectors</a></li></ul></div>
         </td>
         <td valign="top">
           <div class="navigation">



Mime
View raw message