AW: InOut exchange pattern on Transactional JMS endpoint not working

th its own sender-ID. Cheers Stephan -Ursprüngliche Nachricht- Von: sujin sr Gesendet: Mittwoch, 7. August 2019 09:37 An: users@camel.apache.org Betreff: Re: InOut exchange pattern on Transactional JMS endpoint not working Thanks Claus Ibsen for the response. So If I process reply

Re: InOut exchange pattern on Transactional JMS endpoint not working

Hi Claus Ibsen , Could you please provide some input on the previous queries? Thanks. On Wed, 7 Aug 2019 at 13:07, sujin sr wrote: > Thanks Claus Ibsen for the response. > > So If I process replyQueue via a separate route I am wondering about the > below two points > 1. How I can transfer

Re: InOut exchange pattern on Transactional JMS endpoint not working

Thanks Claus Ibsen for the response. So If I process replyQueue via a separate route I am wondering about the below two points 1. How I can transfer requestMessage headers values to the replyMessage headers. 2. I want to get the replyMessages only send from my producer alone, how to listen on

Re: InOut exchange pattern on Transactional JMS endpoint not working

Hi You cannot do request/reply via reply queues with InOut and with transactions as its a chicken/egg situation. The message that is sent to the request queue (for req/reply) is not committed until the transaction is committed and therefore the received cannot "see" the message. On Wed, Aug 7,

InOut exchange pattern on Transactional JMS endpoint not working

Hi, I have a use case where two jms queues are available those are DataRequestQueue and DataReplyQueue. Where If I sent a message to the DataRequestQueue MDB will process the message and send the response to DataReplyQueue. I have used Camel to send the message and receive the response. I have