Hi If you do request/reply over JMS in a Camel route then it correlates and waits for the expected reply message.
So you can do from X to jms foo ? replyTo = bar to Z Where the jms endpoint is doing request/reply over JMS And you can have multiple routes doing request/reply over JMS as well, and also use shared/exclusive queues etc Read more about this on the JMS page at: http://camel.apache.org/jms from X2 to jms foo ? replyTo = bar to Z2 from X3 to jms foo ? replyTo = bar to Z3 On Sat, Jan 4, 2014 at 9:38 PM, yashgt <yas...@gmail.com> wrote: > Perhaps my post was not clear enough... > > Route 1 send M1 to the target service over MQ1 and waits for the target to > respond back with message M2 on MQ2. > > Now, like Route1, there are many other routes that expect different > messages. > > RouteX expects MX to come on MQ2. RouteY expects MY to come on MQ2. > > The solutions so far indicate that I should keep consuming from MQ2 till I > get M2 and then proceed with Route1. This means the RouteX and RouteY will > never get the messages as they have been consumed by Route1. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Asynchronous-processing-of-routes-tp5745385p5745542.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
