I just wrote a test and verified I can set the timeout value on the second cxf endpoint without any trouble. What's the error did you get?
BTW, you should get the socket read time out as you set the receive time out to 1 mill second. -- 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 2:16 PM, ravi.4indra wrote: > I am still having that problem.I had removed responseContext,RequestContext > from the inMessage and added a requestContext with a new ClientPolicy .Do i > to remove any other headers? > > below is the code snippet > > exchange.getIn().removeHeader(Client.RESPONSE_CONTEXT); > exchange.getIn().removeHeader(Client.REQUEST_CONTEXT); > Map<String, Object> requestContext = new HashMap<String, Object>(); > HTTPClientPolicy clientPolicy = new HTTPClientPolicy(); > clientPolicy.setReceiveTimeout(1); > requestContext.put(HTTPClientPolicy.class.getName(), clientPolicy); > exchange.getIn().setHeader(Client.REQUEST_CONTEXT , requestContext); > > Thanks > Ravi > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Timeout-on-a-route-tp5721576p5721692.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
