From: Kirk Haines <khaines@...>
Date: 2004-08-18T05:49:29+09:00
Subject: Re: WEBrick deadlock under Cygwin

On Wed, 18 Aug 2004 04:40:57 +0900, Mark Probert wrote
> Hi, all.
> 
> I am using IOWA / Webrick on Cygwin (DLL version: 1.5.10) under 
> Win2k and I have just started experiencing some problems (hung 
> session, page not displaying, that kind of thing).
> 
> One of the sessions crashed with the following:
> 
> [2004-08-17 12:28:14] INFO  WEBrick 1.3.1
> [2004-08-17 12:28:14] INFO  ruby 1.8.1 (2003-12-25) [i386-cygwin]
> 
> [2004-08-17 12:28:14] INFO  Iowa::HTTPServer#start: pid=2436 port=8080
> probertm-3.corp.nortel.com - - [17/Aug/2004:12:28:19 GMT-8:00] "GET 
> / HTTP/1.1" 200 1656 - -> / deadlock 0x103c7c68: sleep:S  -
 /usr/lib/ruby/1.8/webrick/httpresponse.rb:303
> deadlock 0x103cde00: sleep:S  - 
> /usr/lib/ruby/1.8/webrick/httpresponse.rb:303
> deadlock 0x100f5a18: sleep:F(55) (main) - 
> /usr/lib/ruby/1.8/webrick/server.rb:91
> [2004-08-17 12:29:38] ERROR fatal: Thread(0x100f5a18): deadlock
>         /usr/lib/ruby/1.8/webrick/server.rb:91:in `accept'
> 
> Any ideas?

Hmm.  That is interesting.  Is it something that only happens sporadically?  
Is it load related?  i.e. if you go and use a load testing tool to hammer 
the snot out of it, can you cause it to happen?

I don't have the Cygwin Ruby.  I'm running the one click installer Ruby on a 
standard XP dist, and I haven't seen that, but I'd love to try to reproduce 
it.  I'm going to go start a process to just hammer the crap out of it so 
that I have a lot of threads going and see if I can get that to happen.


Kirk