Specify whether strict message order is preserved for a bus destination
Change the configuration properties of a bus destination to control whether strict message order is preserved.
The changes made in this task affect the configuration of a bus destination. Before beginning this task, make sure that you fully understand the restrictions that apply to ordered destinations. For further details see Strict message ordering for bus destinations.
Although messages produced by a single producer to a single destination are seen by a consumer to that destination in the same order as they are produced, there are certain topologies and events, such as system failures, that can change the order of messages (see Message ordering). If strict message order is essential, we can configure a destination to preserve the order of the messages in a more rigorous manner. Configuring a destination in this way, when used with restricted topologies, maintains message order in all circumstances (for further information, see Strict message ordering for bus destinations).
To preserve the order of the messages that are delivered to a destination, use the administrative console to complete the following steps:
Tasks
- Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations -> destination_name.
- Select the Maintain strict message order check box (setting the option to true).
- Click OK.
- Save changes to the master configuration.
An ordered destination has priority over several other configuration properties, such as the number of consumers allowed to attach to the destination. The system overrides these configuration properties at run time, and generates a system log warning. For more information about the configuration properties the system overrides at run time, and the impact of including an ordered destination in the system, see Strict message ordering for bus destinations.
Related:
Strict message ordering for bus destinations