Pete, i had a problem with mongrel sleeping and resulting in errors (I think 404). It essentially made it look like the app wasn't running and then it would (reluctantly) start after a browser refresh. I can't remember the specific error. Anyway, my solution was to create a script that polled my rails apps every 15 minutes to an hour and kept them alive.
This might be something completely different, but it sounds somewhat similar. John On 5/14/07, Pete DeLaurentis <[EMAIL PROTECTED]> wrote:
Anybody seen this message before? I see it over and over in one of my mongrel processes log files. I've never seen it before today. /usr/local/bin/mongrel_rails:16Mon May 14 20:44:30 +0000 2007: Error calling Dispatcher.dispatch #<Mongrel::TimeoutError: Mongrel timed out this thread: shutdown>Thread #<Thread:0x2ae6288dbc40 sleep> is too old, killing. Thanks, Pete _______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users