On Friday, November 2, 2012 at 11:30 AM, ravi.4indra wrote:
> Hi,
>
> I am seeing the below behaviour with camel-jms component.
>
> inOut("jms:queue:quename?replyTo=queue1&requestTimeOut=30000")
> to("direct:nextRoute");
>
> I think requestTimeOut is the time camel will wait to get response from the
> queue.
> But I noticed that the total timeout for the route is set to 30000 ms. If my
> route takes more that 30000ms i am getting timeout exception. Is this the
> expected behaviour?
The requestTimeOut is for the JmsProducer which will wait for the replay within
the timeout time.
It is not the time for the route.
>
> and also noticed the thread JmsreplyTimeoutChecker running all the time what
> is this thread for?
I think you means JmsReplyManagerTimeoutChecker, it's a thread pool for the
ReplayManager which will wait for the response and correlate the response with
request by using the correlation id.
>
> Any information is appreciated.
>
> Thanks
> Ravi
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/CAMEL-JMS-Request-TimeOut-tp5722000.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
