WildFly HornetQ Message Redelivery on Failure and the Dead Letter Queue: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 13: Line 13:


<pre>
<pre>
...
<address-settings>
<address-settings>
                    <address-setting match="#">
    <address-setting match="#">
                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
        <redelivery-delay>0</redelivery-delay>
                        <redelivery-delay>0</redelivery-delay>
        <max-delivery-attempts>10</max-delivery-attempts>
                        <max-size-bytes>10485760</max-size-bytes>
        ...
                        <page-size-bytes>2097152</page-size-bytes>
    </address-setting>
                        <address-full-policy>PAGE</address-full-policy>
</address-settings>
                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
...
                    </address-setting>
</pre>
                </address-settings>


</pre>
The default redelivery attempt count is 10.

Revision as of 17:51, 25 April 2017

Internal

Overview

If HornetQ fails to deliver a message, its default behavior is to retry delivery to the consumers of the destination for a set number of times. If all subsequent redelivery attempts fail, HornetQ will send the message to a configurable dead letter queue.

Configuration

Redelivery behavior (redelivery count, redelivery delay and the dead letter queue) is configurable on a per-address basis.

...
<address-settings>
    <address-setting match="#">
        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
        <redelivery-delay>0</redelivery-delay>
        <max-delivery-attempts>10</max-delivery-attempts>
        ...
    </address-setting>
</address-settings>
...

The default redelivery attempt count is 10.