Careful with the word "easily" :) As long as you can establish some kind of order a resequenced can put things back in order even though they may be processed in parallel and that is an important distinction. If, on the other hand you truly need to process them in a specific order whereby each message has a dependency upon the completion of another and such order is not determinable at build time, then a routing slip is called for. Do keep in mind, though, that if you send a message to a JMS queue with InOut Semantics then the route will wait for a reply to that message before proceeding and in essence give you a synchronous model on an asynchronous pattern. It all depends on how you want to process. Many systems are a mix of both strategies.
For example consider a system where a group of orders are sent out to bidders who bid on the order. The group of orders may need to be executed in order but each bid is entirely asynchronous. So it would be appropriate to send all orders in parallel to bidders, collect responses for a reasonable amount of time (discarding late arrivals) and then re-sequence the orders and continue processing the overall business case. Such a use case could be implemented using a mix of synchronous and asynchronous EIPs. Hope that helps! :) *Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Maintainable Java (Kindle <http://www.amazon.com/Maintainable-Java-Robert-Simmons-Jr-ebook/dp/B00AKHI69K>)(iTunes <https://itunes.apple.com/us/book/maintainable-java/id585666097?mt=11>)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Sun, Jun 22, 2014 at 5:51 AM, Darwish <othman.darw...@progressoft.com> wrote: > Thank you this is also helpful & i think by mixing some EIP the problem > easily solved :) > > > > > > ----- > Othman Darwish > ProgressSoft Corp. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Consuming-messages-from-multiple-AMQ-queues-and-forward-it-to-single-AMQ-queue-concern-tp5752514p5752665.html > Sent from the Camel - Users mailing list archive at Nabble.com. >