I don't recall seeing Rails/Mongrel making decisions towards how long a thread should last. So I'd say the best way out of making sure you wrap in a terminator/timeout block any operation that *can* end up blocking forever.
On Thu, Nov 20, 2008 at 10:35 AM, Nathan de Vries <[EMAIL PROTECTED]> wrote: > > On 19/11/2008, at 9:40 PM, Andrew Foster wrote: >> Does anyone know how I can clean these up as I go? > > Session#execute should be reaping its own threads (if it's not, that's > a bug). If Session is left doing its thing for too long (greater than > 60 seconds, I believe), it will be holding up the workers in Mongrel's > ThreadGroup and Mongrel will annihilate your worker as best as it can. > Wrapping your call to SSH in a Timeout/Terminator block might fix > things, but I'm not too sure about that. > > -- > Nathan de Vries > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
