On 3/4/06, Garrett Rooney <[EMAIL PROTECTED]> wrote: > Doing more than this may or may not work. For example, if you use > rails scaffolding to create a model, view, and controller for some > object you'll be able to view some pages, but some will hang. Oddly, > clicking on links that direct you to another part of the app often > seem to hang, but cutting and pasting the same URL into the address > bar of the browser will work fine. I still need to figure out what's > causing this, but I suspect a problem in mod_proxy_fcgi, because when > you break into httpd with a debugger you find it sitting in apr_poll.
And it turns out that the underlying problem was simply that we were holding open connections to the back end fastcgi processes, and it was very easy to end up in a situation where all your connections were already being used up. I'm sure this won't be the final word on the subject, but for now I've set the default to closing the connection after each request, which kinda sucks, but at least lets things function reliably. We'll probably want to come up with a better solution in the future anyway, especially when we're actually managing the fcgi processes ourselves instead of requiring them to be managed externally as we are now. -garrett
