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