On Tue, 2006-08-15 at 14:56 -0700, Vasantha Tammana (vtammana) wrote: > Hi, > > I have connection timeout set on HttpConnectionManager > (MultiThreadedHttpConnectionManager.getParams().setConnectionTImeout(x)) > . It seems to be not taking effect i.e it does not timeout at the end of > timeout time when there is no response. > Vasantha,
I suspect you are confusing the socket timeout with the connect timeout. Make sure that you set the socket timeout either at the connection manager level, or at the host level, or at the method level > I remember reading some mailing archives on HttpClient that the timeout > on HostConfiguration takes precedence than the ConnentionManager etc. > Can somebody clarify the precedence on params settings with > HostConfigurations, ConnectionManager, HttpClient and finally GetMethod? > The _socket_ timeout value, if set, takes precedence in the following order: method, host, connection manager, agent > It is really confusing, because you can set the connection timeout in > params at each layer. This is not quite the case. The _connect_ timeout can be set either at the connection manager level or at the agent level Hope this helps Oleg > > > Any help is really appreciated. > > > Thanks, > - Vsantha > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
