WildFly HornetQ Message Redelivery on Failure and the Dead Letter Queue: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
* [[WildFly_HornetQ-Based_Messaging_Subsystem_Configuration#Subjects|WildFly HornetQ-Based Messaging Subsystem Configuration]] | * [[WildFly_HornetQ-Based_Messaging_Subsystem_Configuration#Subjects|WildFly HornetQ-Based Messaging Subsystem Configuration]] | ||
* [[HornetQ_Address_Settings#Message_Redelivery_on_Failure_and_the_Dead_Letter_Queue|HornetQ Address Settings]] | |||
=Overview= | =Overview= |
Revision as of 17:47, 25 April 2017
Internal
Overview
If HornetQ fails to deliver a message, it's default behavior is to retry delivery to the consumers of the destination for a set number of times. If the redelivery fails for all configured redelivery attempts, 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> <expiry-address>jms.queue.ExpiryQueue</expiry-address> <redelivery-delay>0</redelivery-delay> <max-size-bytes>10485760</max-size-bytes> <page-size-bytes>2097152</page-size-bytes> <address-full-policy>PAGE</address-full-policy> <message-counter-history-day-limit>10</message-counter-history-day-limit> </address-setting> </address-settings>