Hi all,<br><br>We use mongrel behind apache (using mod_proxy_balancer) to run an internal app for our business. Lately we've been seeing frequent errors from some of our mongrel processes. <br><br>[Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] (70007)The timeout specified has expired: proxy: error reading status line from remote server
<a href="http://127.0.0.1">127.0.0.1</a>, referer: http://<long-running-request><br>[Sun Dec 16 08:48:47 2007] [error] [client <CLIENT1>] proxy: Error reading from remote server returned by /<long-running-request>, referer: http://<long-running-request>
<br>[Sun Dec 16 08:49:08 2007] [error] [client <CLIENT2>] (70007)The timeout specified has expired: proxy: error reading status line from remote server <a href="http://127.0.0.1">127.0.0.1</a><br>[Sun Dec 16 08:49:08 2007] [error] [client <CLIENT2>] proxy: Error reading from remote server returned by /<not-so-long-running-request>
<br><br>The problem seems to be that the long-running request hogs a mongrel process, and when apache sends the next request to it (after a round-robin tour through the other 9 mongrels), that request times out too. The original action eventually comes back, but sometimes not for several minutes, so we can timeout on many requests in a row.
<br><br>I've seen problems like this mentioned in the context of file uploads (which explain some of our long-running requests), but I've never seen a fix posted. Maybe I haven't looked hard enough? Does anyone know of a config fix that will skip over these blocked processes?
<br><br>Thanks!<br>Mike<br><br>