activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r961614 - in /websites/production/activemq/content: cache/main.pageCache message-redelivery-and-dlq-handling.html
Date Wed, 12 Aug 2015 11:21:43 GMT
Author: buildbot
Date: Wed Aug 12 11:21:43 2015
New Revision: 961614

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/message-redelivery-and-dlq-handling.html

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

Modified: websites/production/activemq/content/message-redelivery-and-dlq-handling.html
==============================================================================
--- websites/production/activemq/content/message-redelivery-and-dlq-handling.html (original)
+++ websites/production/activemq/content/message-redelivery-and-dlq-handling.html Wed Aug
12 11:21:43 2015
@@ -170,7 +170,9 @@ policy.setMaximumRedeliveries(2);
 ...
 </broker>
 </pre>
-</div></div><h3 id="MessageRedeliveryandDLQHandling-TheDiscardingDLQPlugin">The
Discarding DLQ Plugin</h3><p>A very simple yet very useful plugin to the broker.
This plugin allows the configuration of queues and topics, all or matched based on <a shape="rect"
class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html"
rel="nofollow">Java SE regular expressions</a>, to drop messages that have been sent
to the DLQ. This is extremely useful when using <a shape="rect" href="slow-consumer-handling.html">constant
pending message limit strategy</a> or the other eviction rules, but you don't want to
incur the overhead of yet another consumer to clear the DLQ.</p><p>Below is an
example of a basic configuration to drop everything:</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+</div></div><h3 id="MessageRedeliveryandDLQHandling-TheDiscardingDLQPlugin">The
Discarding DLQ Plugin</h3><p>&#160;</p><p>&lt;note&gt;:
from 5.9 - a destination policyEntry supports a deadLetterStrategy of discarding,</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;deadLetterStrategy&gt;&lt;discarding/&gt;&lt;/deadLetterStrategy&gt;</pre>
+</div></div><p>that does the same thing as this plugin but on a per destination
basis. The matching based on regular expressions of the plugin is a bit more powerful than
destination matching so the plugin may still be useful in some cases. &lt;/end note&gt;</p><p>&#160;</p><p>A
very simple yet very useful plugin to the broker. This plugin allows the configuration of
queues and topics, all or matched based on <a shape="rect" class="external-link" href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/regex/Pattern.html"
rel="nofollow">Java SE regular expressions</a>, to drop messages that have been sent
to the DLQ. This is extremely useful when using <a shape="rect" href="slow-consumer-handling.html">constant
pending message limit strategy</a> or the other eviction rules, but you don't want to
incur the overhead of yet another consumer to clear the DLQ.</p><p>Below is an
example of a basic configuration to drop everything:</p><div class="code panel pdl"
style="border-width: 1px;"><
 div class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">&lt;beans&gt;

   &lt;broker ...&gt;
     &lt;plugins&gt;



Mime
View raw message