camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: JMS message selector problem with IBM MQ when doing request/reply (MEP InOut)
Date Sat, 01 Feb 2014 08:00:17 GMT
On Fri, Jan 31, 2014 at 10:44 PM, Fernando Giorgetti
<fgiorgetti@gmail.com> wrote:
> Claus, thanks for the quick reply.
>
> I did it some tests and it seems to work, but can you help me understand
> what is really happening behind the scenes?
>
> Looking at the camel code, it will add a header to the JMS message using a
> unique ID (generated by camel) as a value and the name I gave as the header
> key (which will be used by the selector to retrieve replies from the shared
> queue, so that particular JVM will only get replies for that
> endpoint/selector).
>
> Thus each running camel instance will be able to retrieve the replies
> exactly for the messages they produced, and Camel will still be able to
> return them to the respective producers, based on the original
> JMSCorrelationID they set, is that correct?
>
> Thanks a lot for your help,
>

Yeah just make sure to send back that uuid header in the replies. And
also do not use the same selector name on the same shared queue for
other routes / Camel apps etc.



> Fernando
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/JMS-message-selector-problem-with-IBM-MQ-when-doing-request-reply-MEP-InOut-tp5746670p5746678.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@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

Mime
View raw message