> Excellent investigation and evidence.  I hope you continue, and then do
> something with it (i.e., a bug report to the appropriate forum).
I will report any progress here.


> When you say 100%, do you mean the usage goes up and then bounces 
> around, say between 95% and 100%?
> Or do you mean it flatlines at exactly 100%, with no bouncing?
$ top shows that it's locked at 100% From time to time anew ruby1.8 
process pops in then goes away, but all locked ruby1.8 processes are at 
16.7 to 17% in cpu usage and 8.4 to 8.5 memory usage.

> How are your unit tests doing? Do they cover all this logic, so they 
> might show a similar loop or dead spot?
Nearly 99% of the code is covered and they all pass.

> Can you "comment out" entire blocks of your app
Yes that's what I am doing right now. I have commented out 100% of my 
models code, unloaded a few not frequently updated plugins, and 
commented out all model calls in my controllers, so only empty pages 
will get returned.

I'll see how it works out. The problem is that the last failure happened 
after 8 hours of working perfectly, so I can't tell if it worked or not 
unless I wait at least that amount of time if it doesn't fail before.

> Total shot in the dark: resource acquisition deadlock?  I seem to recall 
> that Passenger runs a cluter of Mongrels
I switched from Thin, to pure mongrel to Passenger, and they all failed 
pretty much the same way, but I'll keep that in mind just in case, and 
try with one Webrick running alone.


Thank you all for your assistance, I need new eyes on this problem as I 
am sure I'm not looking in the correct place.
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to