Hi rainer,For case 70007, the timeout expired, in access log , i've got a 300 second timeoutIn the same time, tomcat's access log haven't any trace of the corresponding request.
For these request, response time is about 30-100msApache is Apache/2.2.17Tomcat is 6.0.26 (jdk1.6.0_24)I'm preparing a tcpdump on each side to see if i can see something received by tomcat .Ivan--On 25 July 2012 11:02, Rainer Jung <rainer.jung@xxxxxxxxxxx> wrote:
On 25.07.2012 09:52, ivan Gouin wrote:Maybe the Timeout has expired?
Hi,
I've got those error in my httpd error log:
[Wed Jul 25 08:10:55 2012] [error] (70014)End of file found: proxy:
prefetch request body failed to *.*.*.*:50300 (...) from ..... ()
[Wed Jul 25 00:13:18 2012] [error] (70007)The timeout specified has
expired: proxy: prefetch request body failed to to *.*.*.*:50300 (...)
from ..... ()
Add %D to your Tomcat and Apache Access Logs. It is the response time in milloiseconds (Tomcat) resp. microseconds (Apache). If the number is e.g. slightly above 60000000 for Apache and you had set a timeout of 60 seconds, then you know the problem is that the response takes to long. You can then check Tomcats Access Log to see how long it actually took. If it really takes to long in Tomcat, then take thread dumps to analyze and switch to the Tomcat users mailing list.
Those error occurs with client accessing a tomcat WS through mod_proxy .
Not all the requests are rejected for today, 416 out of 2194 got one of
these errors.
don't really know how to proceed to debug this error.
thanks for your help
HTH.
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
Ivan GOUIN
|