/Have you seen the section on the Camel JMS doc page about request/reply over JMS? / Yes.
/I assume you mean request/reply over JMS, where the caller waits for the reply? / Exactly. /If you do request/reply over a JMS queue, you need a consumer on the processingQueue to pickup the incoming message, process that message, and send back the reply according to the JMSReplyTo header. If not then there is no reply going back to the caller, and it will timeout. Camel timeout by default after 20 seconds. / So, is my consumer the one that must send the message to replyTo? Have I to write the code for that at the end of my /process/ method? I thought Camel was responsible to check when my /process /method ends and send the message to replyTo queue automatically . /What do you want to do? If you disableReplyTo then you do not do request/reply over JMS. But use one-way messaging. That is an Event Message in the EIP terms http://camel.apache.org/event-message.html/ Forget It! I was a little confused when tried this approach. Now I understand what is happening. Perhaps I was doing something wrong when setting up the reply to queue. So the messages was set to processingQueue and they are consumed but Camel was not able to send this consumed message to replyTo queue. After check some examples and read(and re-read) the docs I could setup my routes and the messages are conumed from processingQueue and then sent to reply queue. Thanx for your reply. -- View this message in context: http://camel.465427.n5.nabble.com/Too-slow-JMS-pipeline-when-disableReplyTo-false-tp5642225p5645106.html Sent from the Camel - Users mailing list archive at Nabble.com.
