>> I don't recall seeing Rails/Mongrel making decisions towards how >> long a thread should last.
... as in killing my requests that go over 60 seconds, or for that matter, any number of seconds. My understanding from the original question was that there were hanging processes sitting there because of (?) ssh connections there weren't closed(?). > I'm experimenting with the Session class > (http://raa.ruby-lang.org/project/session/) to make some SSH calls from > a RoR app. It's working fine only it leaves leftover threads (actually, > bash processes) around. Then I read the rest of the email. So nevermind. ps: I still think that wrapping said connections in a terminator/timeout block would solve the problem though. On Thu, Nov 20, 2008 at 11:15 AM, Nathan de Vries <[EMAIL PROTECTED]> wrote: > > On 20/11/2008, at 10:25 AM, Julio Cesar Ody wrote: >> I don't recall seeing Rails/Mongrel making decisions towards how >> long a thread should last. > > You might want to take a look at Mongrel#initialize then. In > particular, the default timeout value of 60 seconds. When Mongrel > receives a TERM signal and calls Mongrel#graceful_shutdown, it uses > that timeout value to determine if any of the workers have been > running too long. If a thread in one of the workers has been running > longer than 60 seconds, the timeout will have been exceeded and > Mongrel will raise a TimeoutError on that worker thread. > > > Cheers, > > -- > 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
