Hi, Just yesterday we had a problem with the same symptoms. We corrected it by setting the Content-Length header. Are you sure that you have the correct value for Content-Length?
Alex >>>>> "Sebastian" == Sebastian Klenk <[EMAIL PROTECTED]> writes: Sebastian> To: Tomcat Users List <[EMAIL PROTECTED]> Sebastian> Subject: Re: RES: TCP-FIN problem Sebastian> Date: Tue, 23 Dec 2003 18:36:53 +0100 Sebastian> I already send some more code, and if it helps the (FIN,ACK) comes Sebastian> from tomcat and my app responds with a (ACK) imediatelly, then the Sebastian> connection is closed. but it takes aproximatly 30 seconds till the Sebastian> (FIN,ACK) is send after all data has been send. So it looks like Sebastian> this: Sebastian> ... connection established ... Sebastian> APP: request > :TOMCAT Sebastian> APP: < data :TOMCAT Sebastian> ... 30 sec. ... Sebastian> APP: < FIN,ACK :TOMCAT Sebastian> APP: FIN > :TOMCAT Sebastian> ... connection closed Sebastian> Philipp Taprogge wrote: >> Hi! >> >> Sebastian Klenk wrote: >> >>> actually i thought that tomcat was supposed to close the connection after >>> all data has been send - if not this explains a lot! >> >> >> It does, but TCP handshakes are no one-way street. I can only do wild >> guesses from here, but what I think is happening is >> this: after tomcat sends the last chunk of data, your application does >> not release it's hold on the connection, just like as it wants to send >> more data toward tomcat. After not doing so for a given time (60 seconds) >> tomcats assumes that the client on the other side has died and reaps the >> connection. In your code, what is "Receiver"? Where do you get it from? >> >> Phil >> >> >> --------------------------------------------------------------------- To >> unsubscribe, e-mail: [EMAIL PROTECTED] For >> additional commands, e-mail: [EMAIL PROTECTED] >> >> -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
