Oh, there is a thing I didn't point out , when we set the time out value on through the message header, CXF will do a merge with the default configuration and take the min one. So it could be better you setup a big time out value on the default.
-- 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 On Monday, October 29, 2012 at 5:52 AM, ravi.4indra wrote: > Hi, > > I am using camel-CXF component.I am suspecting that the request context is > being cached somewhere in the cxf/camel code thats the reason new timeout > value is not honored. > > can you please provide a solution for this? > > Thanks > Ravi > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Timeout-on-a-route-tp5721576p5721678.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
