Sometimes it can be useful to ensure that every topic consumer sees messages arriving on the topic in exactly the same order.

Normally we guarrentee the order of all messages sent by the same producer; however due to multi-threading and asynchronous processing, the messages from different producers could arrive in different consumers in different orders.

e.g. if we have producers P and Q sending messages such that at about the same time P sends P1, P2, P3 and Q sends Q1, Q2. Then 2 different consumeres could see messages arrive in this order...

i.e. each producers messages are in order; but the streams of messages across producers can get intermixed.

Total ordering of a destination in ActiveMQ ensures that each consumer will see the same total order on that topic. This has a peformance cost, since more synchronization is required, but can be useful - e.g. particularly in times when you want to implement very fast optimistic transactions. With total ordering the messages would arrive like this...

Configuring Total Ordering

Enable the <strictOrderDispatchPolicy/> on the Per Destination Policies. Here's an example

© 2004-2011 The Apache Software Foundation.
Apache ActiveMQ, ActiveMQ, Apache, the Apache feather logo, and the Apache ActiveMQ project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram