Thanks Wayne. After some further investigation, my suspicion is on
the Lighttpd web-server.
When I run in development mode with Mongrel using web-brick the
timeouts don't happen at all. This indicates it's not a mongrel or
rails / ORM issue.
It makes sense that web-servers would have some timeouts for long
running requests. Now I just have to find the switch where I can
tweak them.
Thanks,
Pete
On Nov 7, 2007, at 4:58 AM, Wayne E. Seguin wrote:
On 11/2/07, Pete DeLaurentis <[EMAIL PROTECTED]> wrote:
Hi guys,
Does anyone know if mongrel has a built-in timeout for requests that
take too long? If so, how do you increase it?
I've found that some server requests are timing out. Complicated
requests are already being farmed out to asynchronous processes. But
some of the more basic requests are timing out when we have our peak
server load in the mornings (the bottleneck is the database server).
There are a couple possible locations for the timeout I'm seeing:
1. Mongrel
2. Lighttpd
3. Client browser / application
On my local development server, it does not timeout, leading me to
believe it's not #3.
Any feedback is appreciated.
Thanks,
Pete
Pete,
Run the Mongrels in debugging mode and see what you can glean from
this. If this is DB caused then the timeouts are more likely caused
by an ORM timeout.
Let us know,
~Wayne
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users
