Hi Ivan,
On 03.08.2012 17:23, ivan Gouin wrote:
Here's what i see on the tcpdump:
Got a TCP connect 3-way handshake. (SYN/SYN-ACK/ACK)
Got 7 POST request who got a return code 200
After the 7 POST, got a [ FIN, ACK] from th server.
Then RST from the server
Then the 8th request who goes in time out
Is there some kind of timeout in a tcp keep alive?
Your information is a bit to short. AFAIR we have three communication
nodes, client, proxy and origin server. In addition there was a timeout
happening suspected.
Your info on packets doesn't contain enough about who is communicating
("return code 200", "the server") not about the timing (what time
intervals are between packets.
Regards,
Rainer
On 25 July 2012 11:29, ivan Gouin <gouin.i...@gmail.com
<mailto:gouin.i...@gmail.com>> wrote:
Hi rainer,
For case 70007, the timeout expired, in access log , i've got a 300
second timeout
In the same time, tomcat's access log haven't any trace of the
corresponding request.
For these request, response time is about 30-100ms
Apache is Apache/2.2.17
Tomcat 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.j...@kippdata.de
<mailto:rainer.j...@kippdata.de>> wrote:
On 25.07.2012 09 <tel:25.07.2012%2009>:52, ivan Gouin wrote:
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 ..... ()
Maybe the Timeout has expired?
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
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.
HTH.
Rainer
------------------------------__------------------------------__---------
To unsubscribe, e-mail: users-unsubscribe@httpd.__apache.org
<mailto:users-unsubscr...@httpd.apache.org>
For additional commands, e-mail: users-h...@httpd.apache.org
<mailto:users-h...@httpd.apache.org>
--
*Ivan GOUIN**
*
***Mob (Suisse**)* : +41 (0)79 94107 90
*Mail* : gouin.i...@gmail.com <mailto:gouin.i...@gmail.com>
--
*Ivan GOUIN**
*
***Mob (Suisse**)* : +41 (0)79 94107 90
*Mail* : gouin.i...@gmail.com <mailto:gouin.i...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
