WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Specifying an exception bus destination

Use this task to specify an exception destination to handle messages that cannot be delivered to their intended bus destination.

Why and when to perform this task

You only need to complete this task if you want a bus destination to use a non-default exception destination for undeliverable messages. In this task, the bus destination for which you are specifying an exception destination is referred to as the "intended bus destination".

Each messaging engine has a default exception destination, named _SYSTEM.Exception.Ddestinaton.me_name. This exception destination can be used to handle messages that cannot be delivered for all bus destination that are localized to the messaging engine. This enables administrators to access at one place all messages that cannot be delivered for a messaging engine.

Each bus destination can be configured with a non-default exception destination. This enables administrators to access at a unique place messages that cannot be delivered for the bus destination. An exception destination can be a local or a remote bus destination, but it must be a queue and it must exist when this destination is created. If the exception destination is not a queue or has been deleted when the message arrives, undeliverable messages are rerouted to the default exception destination for the messaging engine.

However, the service integration bus cannot guarantee the ordering of messages sent to an exception destination. Therefore, if message order is important, you can configure a bus destination to not use an exception destination. In this case, the Maximum failed deliveries limit specified for the destination is ignored, and the message remains available to consumers. Synchronous consumers repeatedly attempt to get the message; message-driven beans and other asynchronous consumers are repeatedly driven to consume the message. This can cause an increased load on the system. This situation continues until either the message is removed from the destination (for example, by an administrator using the WebSphere administrative console) or, for whatever reason, the consumer becomes able to process the message without rolling back. Published messages are discarded if there are no subscribers.

To specify a new exception destination for a bus destination, use the administrative console to complete the following steps

Steps for this task

  1. Create the exception destination, as a queue. For information about creating a queue, see Creating a queue for point-to-point messaging.
  2. Type the name of the exception destination in the Exception destination field of the intended bus destination.
    1. In the navigation pane, click Service integration > Buses
    2. In the content pane, click the name of the bus on which the destination is to be created.
    3. In the content pane, under Additional Properties, click Destinations. This displays any existing destinations in the content pane.
    4. Click the destination name.
    5. Type the name of the exception destination in the Exception destination field.
  3. Save your changes to the master configuration.
Related concepts
Bus destinations
Related tasks
Specifying an exception bus destination
Creating a bus destination
Creating a queue for point-to-point messaging
Creating a topic space for publish/subscribe messaging
Creating an alias bus destination
Creating a foreign bus destination
Related information
Destinations collection

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjo0011_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)