Searching for TIME_WAIT turned up this Winsock Programmer's FAQ, which claims that sockets in the TIME_WAIT state are to be expected. IBM suggests some registry keys to change the Windows network stack behaviour to allow for _more_ connections.
Completely unfounded speculation: This might work on Linux/Unix but runs out of sockets on Windows maybe because Windows does not keep track of which TCP connections have both ends local, while Unix keeps track. Then Windows would need to keep those sockets in the waiting state, while Unix knows that it can ignore the issue of outstanding packets as all transfers were local to the machine anyway.
In reply to Re: Socket hang. (Windows or Perl? Solutions?) (Updated)
by Corion
in thread Socket hang. (Windows or Perl? Solutions?) (Updated)
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |