Hi The httpClient.connectionManagerTimeout option doesn't bring the effect you're expecting, see the Javadoc for it's semantics:
http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/params/HttpClientParams.html If an IP-Address can't be resolved you will immediately end up with java.net.UnknownHostException or the likes on the HttpProducer side. Regarding simulating a "Connection Timeout", you could write your own HttpConnectionManager, e.g. do sleep for X seconds before returning a new HttpConnection: http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/HttpConnectionManager.html For this you may want to to decorate the SimpleHttpConnectionManager implementation with the Thread.sleep() calls: http://hc.apache.org/httpclient-3.x/apidocs/org/apache/commons/httpclient/SimpleHttpConnectionManager.html Babak kalyan wrote > Hello, > > I have tried "httpClient.connectionManagerTimeout" in the following way. > > from("servlet:///test") > .process(new MyProcessor()) > .to("http:// > <ipaddress-not-existing> > :8080/context??bridgeEndpoint=true&httpClient.connectionManagerTimeout=1") > > From this I expected it to timeout immediately. However, Camel sends the > request and waits for the response for more than 30 seconds. > > Why is the above example not working ? > > Also, how do I simulate a "Connection Timeout" using camel (need it for a > testcase). > > Thanks in advance. > > -Kalyan -- View this message in context: http://camel.465427.n5.nabble.com/Problem-with-httpClient-connectionManagerTimeout-on-Camel-2-10-4-tp5733367p5733378.html Sent from the Camel - Users mailing list archive at Nabble.com.
