Hi, One more thing I forgot to ask. Right now I am using curl_lib version 7.15.1 and my application don't make use of curl_multi interface. Is it possible that the curl_easy_perform error "couldn't connect to host" (on making rapid web requests) will be resolved with curl_multi interface?? Please give some feedback. Thanks in advance.
Partha. On Thu, Apr 9, 2009 at 8:53 PM, partha koley <[email protected]> wrote: > HI, > Even I faced a similar issue. I don't see any failed TCP connect sequence > in wireshark and the web server is up and running fine. > I guess RTOS is running out of available TCP sockets due to which new HTTP > requests are not being sent out and only after 5-6 seconds everything starts > working fine. > So can we set TIME_WAIT to zero in libcurl and what is the default value > that is already set if any? > Can we control that through lib curl so that the socket does not go into > WAIT state? > > > > > On Thu, Apr 9, 2009 at 5:40 PM, Daniel Stenberg <[email protected]> wrote: > >> On Thu, 9 Apr 2009, Pallavi Agrawal wrote: >> >> I am facing the issue of the curl_easy_perform error "couldn't connect to >>> host" on making rapid web requests. >>> >> >> if you wireshark the network when this happens, don't you see failed TCP >> "connect" sequences? Or is it socket() that fails? >> >> On getting the libcurl error I did inetstatShow and observerd that the tcp >>> sockets get into the TIME_WAIT (as can be seen below). >>> >> >> If they are, I suppose an RTOS could easily run out of available sockets. >> Why are they in TIME_WAIT? Normally they shouldn't be. >> >> -- >> >> / daniel.haxx.se >> > >
