Using the Dead Letter Channel

The Dead Letter Channel (DLC) is a sub-set of a queue, specifically designed to persist messages that are typically marked for deletion, providing you with a choice on whether to delete, retrieve or reroute the messages from the DLC. A DLC queue is created when the first subscription is made for a specific domain (superuser or tenant). By default, the message broker retries a defined number of times, when a subscriber does not acknowledge a message.  Once the retry count has been breached, the message is removed from the queue and placed into the DLC.  The default number of retries is set to 10, however, this value is configurable. For information on how to configure the retry count, see Configuring the Message Retry Count.

Browsing through the DLC Queue

All messages that have breached the retry count will be dumped into the DLC queue. The content of the queue can be viewed by following the steps below:

1. On the main tab in the management console click, Dead Letter Channel - > Browse.
2. The DLC browser is displayed in the right side of the pane, as shown below. The message count defines the number of messages in the DLC queue. 
   
   
3. Click  Browse  under the View column to navigate to each individual message stored in the DLC. The Destination column shows the name of the original queue.
   
   You can choose to delete, restore or reroute one or more messages.
   

   Delete - Permanently delete the message from MB.

   Restore - Re-insert the message to the queue from which the message originated.

   ReRoute - Allows you to select a destination of choice instead of restoring the message to the original queue. When you click ReRoute, a pop-up menu appears, as shown below:

   
   Select the queue name to which the message should be re-routed to and click OK. The message is moved to the relevant queue.

Multitenancy

In order to ensure that messages can be distinguishable per tenant, a separate DLC is created for every new tenant created. The signature of the DLC queue is similar to the example below:

{tenant_name}/DeadLetterChannel

This ensures that only messages exchanged through queues in a specific tenant domain are inserted into the DLC queue.

Configuring the Message Retry Count

The message retry count can be configured as follows:

1. Open the andes-config.xml file located in $MB_HOME/repository/conf/advanced.

2. Locate the maximumNumberOfMessageDeliveryAttempts attribute and change the value accordingly. For example,

   <maximumNumberOfMessageDeliveryAttempts>15</maximumNumberOfMessageDeliveryAttempts>