activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r881831 - in /websites/production/activemq/content: cache/main.pageCache message-groups.html
Date Wed, 09 Oct 2013 10:21:31 GMT
Author: buildbot
Date: Wed Oct  9 10:21:30 2013
New Revision: 881831

Production update by buildbot for activemq


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 Oct  9 10:21:30 2013
@@ -32,15 +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 type="text/javascript"> 
-        SyntaxHighlighter.defaults['toolbar'] = false; 
-        SyntaxHighlighter.all(); 
-      </script> 
     Apache ActiveMQ &#8482; -- Message Groups
@@ -112,6 +103,17 @@
 <ul><li>the consumer closes (or the client which created the consumer dies etc)</li><li>someone
closes the message group by sending a message with a negative value for JMSXGroupSeq (see
below for more details)</li></ul>
+<p>Note: like message selector matching, grouping based on JMSXGroupID occurs before
dispatch on messages in memory. With the default maxPageSize setting, large backlogs of messages
destined for one group they can block receipt of messages to other groups if they don't all
fit in memory. You can change the default maxPageSize setting for destinations as follows:</p><div
class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
+  &lt;destinationPolicy&gt;
+      &lt;policyMap&gt;
+         &lt;policyEntries&gt;
+             &lt;policyEntry queue="&gt;" maxPageSize="1000"/&gt;
+         &lt;/policyEntries&gt;
+      &lt;/policyMap&gt;
+  &lt;/destinationPolicy&gt;]]></script>
 <h3><a shape="rect" name="MessageGroups-UsingMessageGroups"></a>Using Message
 <p>You just need to change your JMS producers to fill in the <b>JMSXGroupID</b>
message header with some String value of your choice. e.g.</p>

View raw message