WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer bus destinations > Configure bus destinations > Configure bus destination properties
Configure exception destination processing for a bus destination
We can configure the exception destination processing for a queue destination or topic space destination. We 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.
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 Create a queue for point-to-point messaging. 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.
We can configure an exception destination for a bus destination as one of the following:
- 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 associated with this destination, or the Blocked retry timeout in milliseconds 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.
- We cannot configure exception destination processing for a bus; configure exception destination processing for each destination on the bus.
- Do not modify or delete the default system exception destination.
- If we use an exception destination for a bus destination, it can affect message ordering in the bus. For more information, see Message ordering.
- 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 dmgr console to complete the following steps.
- In the navigation pane of the dmgr console, click Service integration -> Buses to display a list of buses.
- Select the bus with the destination for which to configure an exception destination.
- In the Configuration tab, under Destination resources, click Destinations to display a list of destinations for this bus.
- Select the name of the bus destination you require from the list. The details of that destination are displayed.
- In the Configuration tab, under General
properties, in the Exception destination section, use the radio buttons to configure the exception destination processing
that this bus destination uses:
- Select None to specify the bus destination does not use an exception destination.
- Select System to use the default exception destination.
- Select Specify and enter an exception destination to configure the exception destination you require.
- Optional: If you selected None, we can set the time interval to apply between retry attempts, after the maximum failed deliveries limit is reached, for this destination. Select Override messaging engine blocked retry timeout default, then enter the value you require in Blocked retry timeout in milliseconds. Otherwise, the value set for the Default blocked destination retry interval of the associated messaging engine is used.
- Optional: To change the number of delivery attempts for a message, enter a value in Maximum failed deliveries per message. When the exception destination is configured as None, this is the number of delivery attempts before a time interval between retry attempts is applied. When the exception destination is configured as System or Specify, this is the number of delivery attempts for a message that is backed out and tried again before the message is sent to the exception destination.
- Optional: Select Keep count of failed deliveries per message to persist the failed delivery counts of JMS messages in the message store. This option retains the count of failed deliveries even after the system is restarted.
New feature:
The Keep count of failed deliveries per message option persists the failed delivery counts of the messages in the message store.
- Save your changes to the master configuration.
Results
You have configured the exception destination processing for a bus destination.
We can also configure exception destination processing for a service integration bus link or WebSphere MQ link.
Related concepts:
Bus destinations
Exception destinations
Related
Create a bus destination
Create a queue for point-to-point messaging
Create a topic space for publish/subscribe messaging
Create an alias destination on a bus
Configure alias destination properties
Create a foreign destination on a bus
Configure exception destination processing for a link to a foreign bus
Related information:
Destinations [Collection]