I have a very strange issue going on that just started happening last week. I am running an apache/mongrel stack on a windows 2003 box connecting to a sql server 2005.
Apache 2.2.3 Mongrel 1.1.5 Since last Thursday I have had 5 crashes where the mongrel service becomes unresponsive. If I restart the service all is fine. Nothing is being reported in the rails logs... But I did notice something in the mongrel logs. Each time it look like I get the following log entry: ** INT signal received. Wed Aug 13 15:01:20 -0500 2008: Reaping 103 threads for slow workers because of 'shutdown' Thread #<Thread:0x8553270 sleep> is too old, killing. Wed Aug 13 15:01:20 -0500 2008: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown> c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:221:in `process' c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:159:in `process_client' c:/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel.rb:158:in `each' I have seen this pattern repeated for each of the crashes. I have 5 instances running and about 50 concurrent users who are banging away at this web application. Any advice or thoughts would be much appreciated. Thanks in advance -- Posted via http://www.ruby-forum.com/. _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
