Hi,

I set timeout for http component of Camel with httpClient.soTimeout=6000, as
described in the Camel documentation. The http endpoint is formed inside a
dynamic router, for each request. But it seems like it is overriden by a
global parameter.  Can anybody shed any light on this? 


2012-02-15 01:15:14,551 | DEBUG | 5-180 - /call | DefaultHttpParams             
  
| 160 - org.apache.servicemix.bundles.commons-httpclient - 3.1.0.5 | Set
parameter http.socket.timeout = 6000 
2012-02-15 01:15:14,590 | DEBUG | 5-180 - /call |
ltiThreadedHttpConnectionManager | 160 -
org.apache.servicemix.bundles.commons-httpclient - 3.1.0.5 |
HttpConnectionManager.getConnection:  config =
HostConfiguration[host=http://10.xx.xx.23:8080], timeout = 0 

Furthermore, that log lines appear only when I call that flow for the very
first time. Next calls only include the second line, i.e. timeout = 0

Infinite timeout is a disaster for my project.. Any help will be very much
appreciated.I am working on Camel 2.6.0 on Smx 4.3.0.

--
View this message in context: 
http://servicemix.396122.n5.nabble.com/Camel-http-component-timeout-tp5484005p5484005.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Reply via email to