search for: bad_controller_act

...creating the bad threads. For example, lets say you see a thread leak. Many times this is caused by trying to make a connection to a remote resource that isn''t there, but you''re not sure. What you do is put this into the suspected controller''s action: Thread.current[:bad_controller_action] = true Or some of other tag to differentiate it with the other threads. Then run Mongrel with -B and if you see this in the KEYS list then you know that this is the controller. MYSQL DROPPED CONNECTIONS? ANYONE? Finally, there seems to be a bug in Rails where it is constantly dropping the...