The previous snippet is from: http://mongrel.rubyforge.org/faq.html
-- Aníbal Rojas http://www.rubycorner.com http://www.hasmanydevelopers.com On Feb 8, 4:54 pm, "Aníbal Rojas" <[EMAIL PROTECTED]> wrote: > >From Q: Mongrel stops working if it's left alone for a long time. > > If you find that Mongrel stops working after a long idle time and > you're using MySQL then you're hitting a bug in the MySQL driver that > doesn't properly timeout connections. What happens is the MySQL server > side of the connection times out and closes, but the MySQL client > doesn't detect this and just sits there. > > What you have to do is set: > > ActiveRecord::Base.verification_timeout = 14400 > > Or to any value that is lower than the MySQL server's > interactive_timeout setting. This will make sure that ActiveRecord > checks the connection often enough to reset the connection. > > Q: Mongrel stops working if it's left alone for a long time. > > If you find that Mongrel stops working after a long idle time and > you're using MySQL then you're hitting a bug in the MySQL driver that > doesn't properly timeout connections. What happens is the MySQL server > side of the connection times out and closes, but the MySQL client > doesn't detect this and just sits there. > > What you have to do is set: > > ActiveRecord::Base.verification_timeout = 14400 > > Or to any value that is lower than the MySQL server's > interactive_timeout setting. This will make sure that ActiveRecord > checks the connection often enough to reset the connection. > > -- > Aníbal Rojashttp://www.rubycorner.comhttp://www.hasmanydevelopers.com > > On Feb 8, 11:07 am, "Bill Walton" <[EMAIL PROTECTED]> wrote: > > > Greetings! > > > I'm in the process of moving my app from a shared hosting arrangement to a > > VPS and am seeing some mongrel behavior I haven't seen before. > > Specifically, after about 30 minutes of inactivity mongrel goes unresponsive > > and has to be restarted. When I restart it writes the messages below. > > Before that, there's nothing in the logs that shows any problem at all. > > > In mongrel.log: > > > ** USR2 signal received. > > Thu Feb 08 08:43:51 EST 2007: Reaping 2 threads for slow workers because of > > 'shutdown' > > Thread # is too old, killing. > > Thu Feb 08 08:43:51 EST 2007: Error calling Dispatcher.dispatch #Thread # is > > too old, killing. > > > In production.log: > > > Mongrel timed out this thread: shutdown > > > A set of trace messages follow this which I'm happy to post if it would be > > helpful. > > > Can anybody help me understand what's going on and what I need to do to fix > > it? > > > Thanks much, > > Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
