Re: How to debug 70014 and 70007 errors

[ivan Gouin <gouin.ivan@xxxxxxxxx>]

Hi Rainer,

Keep Alive Timeout wasn't set on my config 

But its default value of 5 seconds was the reason why the connection closed. 

In fact the root cause is the behavior of the CXF client who didn't take care of the close announcement of this connection.

We're trying to fix this issue but setting the timeout higher solve is a workaround for now.

Thank for your help.

Ivan

On 12 August 2012 13:11, Rainer Jung <rainer.jung@xxxxxxxxxxx> wrote:

On 08.08.2012 16:20, ivan Gouin wrote:

Hi,

Here's more information about my issue:

Here i will call
user : the application  who post the request.
apache : the httpd server who receive request from the client and send
them to tomcat
tomcat: the web server tomcat, a Web Service application

Versions
user : Apache CXF client 2.2.9
apache: httpd 2.2.17 (tried a 2.2.22 too)
tomcat: 6.0.26 (jdk1.6.0_24)

Here's the post request send by user ( * are for anonymise)

POST /***/***/ws/v2?test HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
Authorization: Basic Z3ZkMHRhb2FwcDpkbmVlc3cyYQ==
Accept: */*
User-Agent: Apache CXF 2.2.9
Content-Length: 304
Host: ***
Connection: Keep-Alive

<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">************************</soap:Envelope>

Start at 11:56:57
Between 11:56:57.5357 and 11:56:58:4784: 4 request pass OK

Here's the sequence after that : (Time is of tomcat seem too be a little
shifted, user and apache are on the same host)

11:56:58.4817            user : POST request

*11:56:58.459722tomcatTCP55150300 > 41323 [PSH, ACK] Seq=3187 Ack=3818
Win=22400 Len=485 TSval=345704305 TSecr=749474400 (HTTP 200)*
11:56:58.491981apacheTCP55150300 > 41323 [PSH, ACK] Seq=3187 Ack=3818

Win=22400 Len=485 TSval=345704305 TSecr=749474400 (HTTP 200)

11:56:58.492251userHTTP/XML594HTTP/1.1 200 OK

Did this packet contain the full response?

*11:56:58.501457tomcatTCP6641323 > 50300 [ACK] Seq=3818 Ack=3672
Win=15872 Len=0 TSval=749474449 TSecr=345704305*
11:56:58.531503apacheTCP6641323 > 50300 [ACK] Seq=3818 Ack=3672
Win=15872 Len=0 TSval=749474449 TSecr=345704305
11:56:58.585937userTCP6045501 > 80 [ACK] Seq=2893 Ack=3948 Win=49640 Len=0

5 seconds pause

*11:57:03.492499userTCP5480 > 45501 [FIN, ACK] Seq=3948 Ack=2893
Win=16640 Len=0*

KeepAlive Timeout 5 seconds configured for Apache?

11:57:03.494663userTCP6045501 > 80 [ACK] Seq=2893 Ack=3949 Win=49640 Len=0
11:57:08.694657userTCP335[TCP segment of a reassembled PDU]
11:57:08.694703userTCP5480 > 45501 [RST] Seq=3949 Win=0 Len=0

11:57:08.694661userHTTP/XML358POST /*/*/ws/v2?test HTTP/1.1

11:57:08.694763userTCP5480 > 45501 [RST] Seq=3949 Win=0 Len=0
*11:57:18.466178tomcatTCP6650300 > 41323 [FIN, ACK] Seq=3672 Ack=3818
Win=22400 Len=0 TSval=345724311 TSecr=749474449*
11:57:18.498510apacheTCP6650300 > 41323 [FIN, ACK] Seq=3672 Ack=3818
Win=22400 Len=0 TSval=345724311 TSecr=749474449
*11:57:18.508720tomcatTCP6641323 > 50300 [ACK] Seq=3818 Ack=3673
Win=15872 Len=0 TSval=749494456 TSecr=345724311*
11:57:18.538771apacheTCP6641323 > 50300 [ACK] Seq=3818 Ack=3673

Win=15872 Len=0 TSval=749494456 TSecr=345724311

What make me mad is why apache send a FIN/ACK closing the communication??
Is there a time out somewhere?
This seems to happen about 5 second after the last ACK
Or  6 second the opening of the socket ( at 11:56:57.53)

I guess its the Keep Alive Timeout of 5 seconds configured for Apache. Check configuration.

This should not produce a problem in itself. A client that observes a closed connection when trying to send a follow on request should transparently start a new connection.

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx