You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by bu...@apache.org on 2013/03/07 17:21:37 UTC
svn commit: r853493 - in /websites/production/activemq/content:
cache/main.pageCache message-redelivery-and-dlq-handling.html
Author: buildbot
Date: Thu Mar 7 16:21:37 2013
New Revision: 853493
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 Thu Mar 7 16:21:37 2013
@@ -265,7 +265,7 @@ redeliveryDelay=<span class="code-quote"
<p>The familiar <a shape="rect" href="redelivery-policy.html" title="Redelivery Policy">Redelivery Policy</a> has been extended to take a matching destination.<br clear="none">
fallbackToDeadLetter controls the action when there is no matching redeliver policy for a destination. Defaults to true so regular DLQ processing ensues.<br clear="none">
-sendToDlqIfMaxRetriesExceeded controls the action when the retry limit is exceeded. Defaults to true so regular DLQ processing ensues.</p>
+sendToDlqIfMaxRetriesExceeded controls the action when the retry limit is exceeded. Defaults to true so regular DLQ processing ensues. When false, the message is dropped.</p>
<ul><li>Note: broker schedulerSupport must be enabled for this feature to work.</li></ul>