On 27.10.2008 23:22, cedric so wrote:
> Robert Klemme wrote:
>> Hm...  Is the hosting system a Windows non server version?  That could
>> play a role as well.  Or, your Webrick dies for some reason and hence
>> you cannot connect any more.  There are so many options where network
>> communication can go wrong...
> 
> I tested it both on a Windows non-server and server versions but the 
> results
> were the same. The Webrick does not die because it still accepts 
> connections
> whenever I run the my test program. My only problem is that it doesn't 
> accept
> all the connections.

Did you check connection state with netstat?  It may be that socket 
resources are not released fast enough.  I'm not a network admin but it 
may be that you can remedy this with a changed timeout setting.

Kind regards

	robert