Greetings! Apologies for replying to / reviving such an old thread.
http://camel.465427.n5.nabble.com/JMS-message-selector-problem-with-IBM-MQ-when-doing-request-reply-MEP-InOut-tt5746670.html#none
Fernando originally wrote, that while using WebSphere MQ and a single shared
reply
queue, the gener
On Fri, Jan 31, 2014 at 10:44 PM, Fernando Giorgetti
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
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 h
Try look at the replyToDestinationSelectorName option.
On Fri, Jan 31, 2014 at 6:53 PM, Fernando Giorgetti
wrote:
> Hello,
>
> I am having a problem with the selector used by jms component to fetch the
> reply messages when using MEP InOut (while running a load test).
>
> We have manually shutdow
