]
Mladen Turk closed JBAS-4558.
-----------------------------
Resolution: Out of Date
Cleanup
Connection Timeout Immediately After ACKing A Request
-----------------------------------------------------
Key: JBAS-4558
URL:
https://jira.jboss.org/jira/browse/JBAS-4558
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: JBossAS-4.0.2 Final
Reporter: Mike Millson
Assignee: Mladen Turk
Attachments: drop5.cap
The customer has an application that periodically sends Web service requests to JBoss AS
every 20 secs in sets of 4, to check wether the Web Service is up. They find that JBoss AS
occasionally drops the request packets when the HTTP connector timeout is set to 20
seconds. When this happens, the packet sequence is very strange. Attached is an example
packet sequence viewable using ethereal/WireShark.
#275: Client sends request >20 seconds after #274 acknowledgment
#276: Server sends ACK for #275
#277: Server sends connection timeout FIN/ACK
#278 Client sends combined ACK for #277 and FIN/ACK
#279 Server sends ACK for #278
Packet #275 was more than 20 seconds after the last packet was sent; however, it was
received before the server initiated the connection timeout sequence in packets #277-279.
It seems to be unaware of the ACK in #276. Almost as if the timeout sequence started, then
before the FIN/ACK could be sent, another packet was received and acknowledged. Some sort
of timing issue when a request is sent at the same time a connection times out.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: