search for: mongrel_sleeper_thread

...eavy loads, our mongrels will seg fault and die one by one. Following the advice in a previous thread (http://www.mail- archive.com/mongrel-users at rubyforge.org/msg01734.html), I installed mongrel 0.3.13.5, but the problem remains The line in particular that appears to be breaking is: $mongrel_sleeper_thread = Thread.new { loop { sleep 1 } } Found at line 274 of configurator.rb I do have a core file, but I''m not really proficient with gdb. I can send it along if someone is interested. I''m using JMeter to simulate loads on the server. The mongrels only seem to die under high loads...

...by the patch to sync.rb from the standard library. What is happening here is that when sync_unlock is called Thread.critical is set to true. Now if the thread is not the sync_ex_locker an exception is thrown without Thread.critical being set to false. This in turn resulted in a situation where the mongrel_sleeper_thread (configurator.rb:270) was the only thread getting back on the cpu and Thread.critical stayed true. The patch simply ensures that Thread.critical is set to false upon leaving sync.rb. I am not sure if this is really the correct way to handle this issue though. As some famous programmers have been k...

I have a Rails 1.2.3 app (due for an update, I know) running on a Mongrel 1.1.4 behind Apache 2.2.3 mod_proxy on Debian 4.0. It keeps hanging up for no reason I can tell. I have tried everything that anyone has ever hinted at being a solution for this problem: - The application doesn''t use MySQL, so setting the connection timeout won''t help. - Using AR not PStore for sessions. -