Configuring exception destination processing for a bus destination
You can configure the exception destination processing for a queue destination or topic space destination. You can configure whether any undeliverable messages are rerouted to an exception destination, and whether to use a system default exception destination or configure a specific exception destination.
Before you begin
To configure a specific exception destination for a queue destination or topic space destination, the exception destination must exist. An exception destination must be a queue destination. See Creating a queue for point-to-point messaging.
About this task
An exception destination for a queue destination or topic space destination is the destination for a message when a message cannot be delivered because the number of delivery attempts to a transactional consumer is exceeded.
- None. The bus destination does not use an exception destination and undeliverable messages are not rerouted to an exception destination. Attempts to redeliver the message continue, up to the maximum failed deliveries limit set for the bus destination. Then attempts to redeliver the message continue with a time interval between retry attempts. This interval is either the Default blocked destination retry interval of the messaging engine that is associated with this destination, or the Blocked retry timeout in milliseconds that is set for this destination.
- System. The bus destination uses the default exception destination. Messages that cannot be delivered to the bus destination are rerouted to the system default exception destination for the messaging engine that detects the problem: _SYSTEM.Exception.Destination.messaging_engine_name. This option is the default option.
- Specify. The bus destination uses the specified exception destination. If the bus destination cannot use this exception destination, it uses the system exception destination.
- You cannot configure exception destination processing for a bus; you must configure exception destination processing for each destination on the bus.
- Do not modify or delete the default system exception destination.
- If you use an exception destination for a bus destination, it can affect message ordering in the bus.
- Best-effort messages are always discarded if they cannot be delivered to their target destination, that is, they never use an exception destination.
- Any report options that are set in the properties of a message also affect exception destination processing. Depending on the report options, a message might be discarded if it is not delivered.
To configure the exception destination processing for a bus destination, use the administrative console to complete the following steps.