Hi Dormando,<br><br>Really appreciate your reply.<br><br>In this case, the 'slow server' is a cgi script, so I guess the connection from Perlbal to the slow server will not have http Connection:keep-alive header.<br>
And the cgi script does start sending the data within first few seconds and keeps on sending the data.<br><br>If you think I should NOT be receiving the timeout, please do let me know. I will try to debug it more.<br><br>
On my system, I could reproduce/fix the problem repeatedly by changing max_idle_time(<span style="font-style: italic;">where you mentioned)</span> and restarting perlbal.(Also if I hit the url to the slow server directly taking out the perlbal from the equation, things work fine).
<br><br><br>[ The reason I updated the max_idle time because I saw 'keep_alive' parameter is only updated in the ClientHTTPBase::event_write. <br>So my "theory" was that perlbal will kill the connection to backend slow proxy after 30 sec through Socket::_do_cleanup() function.
<br>event_write will not be called because Perbal will have nothing to write to the slow proxy after it has sent the get request.<br><br>]<br><br><br><br>Thanx,<br>HB<br><br><div><span class="gmail_quote">On 9/17/07, <b class="gmail_sendername">
dormando</b> <<a href="mailto:dormando@rydia.net">dormando@rydia.net</a>> wrote:I <br></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If this is the code you edited:<br><br># FIXME: let this be configurable?<br>sub max_idle_time { 30; }<br><br>... then likely, yes.<br><br>The latest SVN tree has the configurable 'persist_client_timeout'<br>merged. That only appears to affect the keep alives though? If your
<br>server's taking a long time to initially start feeding data back to the<br>client, and you've already established a keepalive connection, this will<br>matter.<br><br>-Dormando<br><br>Hemant Bist wrote:<br>> Hi, I have perlbal running in reverse proxy role. I have a case, where
<br>> the backend mod_perl servers redirect the the perlbal (via X-REPROXY-URL<br>> header) to a server that takes around 2 min to serve all the<br>> data to the browser. I am consistenly getting timeout in less than min
<br>> in such case.<br>><br>><br>> Changing the max_idle_time in ClientHTTPBase.pm to return 180 seems to<br>> fix the problem for me. (But I am not sure if it also increases the<br>> timeout for the persistent browser connections to 180 sec)
<br>><br>> Is this a known bug/behaviour. Or something that I only I am noticing.<br>><br>> I see a patch from Justin to configure the timeout per service in this<br>> list(<a href="http://lists.danga.com/pipermail/perlbal/2007-June/000518.html">
http://lists.danga.com/pipermail/perlbal/2007-June/000518.html</a> ).<br>> Is it to workaround this bug?<br>><br>> Thanx,<br>> HB<br>><br>><br>><br><br></blockquote></div><br>