On 2/26/07, C.jay Martin <[EMAIL PROTECTED]> wrote: > > DBA just got back to me. The user logging in to the table has no > connection limit. That means it has to be either the ADO.rb linking to > SQL Server, or Mongrel's handling of the database...Or unhandled > timeouts... >
Most usual are unhandled timeouts. Mongrel CAN serve 20+ request, but not with Rails, since isn't Thread-Safe and require a big lock around it to avoid random and madness due ActiveRecord: http://mongrel.rubyforge.org/docs/frameworks.html Also pointed in the FAQs: http://mongrel.rubyforge.org/faq.html > How would I go about making a timeout infinite, or handling one? > This is an enterprise grade Database on a server that doesn't get hit > hard... I really don't see why it'd be timeouts, honestly...but I'll > keep the possibility in mind. > Previously you was serving your rails applications with lighttpd and fastcgi, right? That means a bunch of ruby process to "balance" the load of every request that get into lighty. Since you're running one instance (as service), several hits to the same instance will timeout, mostly due slow answers from DB (most of the cases). Could someone contribute more with SQL Server setups? I'm not a user of them, could try to re-create Jays scenario but will take time. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
