Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@www.apache.org Received: (qmail 70788 invoked from network); 23 Dec 2003 17:38:01 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 23 Dec 2003 17:38:01 -0000 Received: (qmail 7371 invoked by uid 500); 23 Dec 2003 17:37:33 -0000 Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org Received: (qmail 7351 invoked by uid 500); 23 Dec 2003 17:37:33 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 7337 invoked from network); 23 Dec 2003 17:37:32 -0000 Received: from unknown (HELO mail4.interscholz.com) (217.6.240.5) by daedalus.apache.org with SMTP; 23 Dec 2003 17:37:32 -0000 Received: from (195.243.187.13 [195.243.187.13]) by MailEnable Inbound Mail Agent with ESMTP; Tue, 23 Dec 2003 18:38:42 +0100 Received: from visions-tec.de (217.230.2.199) by mail2.interscholz.com with MERCUR Mailserver (v4.02.24 MTA1LTIwNTQtNDg3Nw==) for ; Tue, 23 Dec 2003 18:34:52 +0100 Message-ID: <3FE87D35.3050401@visions-tec.de> Date: Tue, 23 Dec 2003 18:36:53 +0100 From: Sebastian Klenk User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: de, en-us, en MIME-Version: 1.0 To: Tomcat Users List Subject: Re: RES: TCP-FIN problem References: <0093347A42A332429FEF9B83B821756C0618AD6E@wtrjo088> <3FE86FE7.9010008@visions-tec.de> <3FE8731D.5080007@gmx.net> <3FE875A1.1030306@visions-tec.de> <3FE8791B.7040009@gmx.net> In-Reply-To: <3FE8791B.7040009@gmx.net> X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I already send some more code, and if it helps the (FIN,ACK) comes from tomcat and my app responds with a (ACK) imediatelly, then the connection is closed. but it takes aproximatly 30 seconds till the (FIN,ACK) is send after all data has been send. So it looks like this: ... connection established ... APP: request > :TOMCAT APP: < data :TOMCAT ... 30 sec. ... APP: < FIN,ACK :TOMCAT APP: FIN > :TOMCAT ... connection closed 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: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org