From: Florian Gross <flgr@...>
Date: 2004-08-18T08:10:56+09:00
Subject: Re: WEBrick deadlock under Cygwin

Kirk Haines wrote:

>>I once was able to reproduce a deadlock using Sockets directly with 
>>the one click installer (on Ruby 1.8.2), but it wasn't reproduceable.
> So, that would indicate that it is a problem with sockets on Windows?  I 
> have not been able to reproduce the original error, but I have found that if 
> I have more than 5 concurrent requests, the code fails.  It looks like the 
> first socket that was opened of the concurrent group gets closed, and that 
> causes Webrick to throw an exception.  An EINVAL from line 303 of 
> httpresponse.rb.

Hm, an EINVAL exception shouldn't cause Thread deadlocks AFAIK. (Thread 
deadlocks are caused by the fatal exception, I think.)

But I think it is related to the implementation of socket.so on Windows.

Regards,
Florian Gross