How do i resolve this issue because this is happening
after the server has been running for a while , i have
tried increasing the timeout parameter value to more
than 500 and still dosen't work ?
sachin
--- Tom Mornini <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2001, Geoffrey Young wrote:
>
> > > I am getting "Apache->read timed out messages
> in my
> > > error_log,now i have been looking at this
> problem for a while
> > > now before posting it for help, whats happening
> is if i test
> > > my application from within the network , because
> the
> > > connection being very fast i am not having any
> problems , but
> > > when i try to do the same thing from the
> external network
> > > over a dial up line i get this error message in
> the error
> > > logs and the script gets killed
>
> I had this problem and it drove me completely nuts
> until I figured it out.
>
> In my case, in a front-end-proxy/back-end-mod_perl
> configuration it turned
> out to be having a lower timeout value for the
> back-end Apaches than for
> the front-end Apaches.
>
> I had set it this way to try and free up back-end
> servers (which are more
> valuable than front-end servers) more quickly in the
> event of a timeout.
>
> It didn't work out that way! :-) I now run 300
> seconds on the front-ends
> and 400 on the back-ends, and Apache->read timeouts
> no longer cause
> problems.
>
> --
> -- Tom Mornini
> -- InfoMania Printing and Prepress
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
