This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
No announcement yet.
What approach when order of processing matters?Page Title Module
The simplest way is just to use a single consumer. Jms guarantees delivery order. If you need more concurrency, you'll have to implement the equivalent of an aggregator..which can be difficult if the messages are received asynchronously. You can use something like an index so that messages contain ordering information and you just cache (in the database or wherever) messages that are received out of sequence. This is similar to how tcp orders packets.