Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 47322 invoked from network); 17 May 2006 15:44:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 May 2006 15:44:33 -0000 Received: (qmail 7169 invoked by uid 500); 17 May 2006 15:44:27 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 7005 invoked by uid 500); 17 May 2006 15:44:26 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 6994 invoked by uid 500); 17 May 2006 15:44:26 -0000 Delivered-To: apmail-jakarta-tomcat-dev@jakarta.apache.org Received: (qmail 6985 invoked by uid 99); 17 May 2006 15:44:26 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 May 2006 08:44:26 -0700 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 May 2006 08:44:25 -0700 Received: by brutus.apache.org (Postfix, from userid 33) id 6E8D571429B; Wed, 17 May 2006 15:43:56 +0000 (GMT) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 39600] New: - A lot of connection in TIME_WAIT state on Tomcat clients Message-ID: X-Bugzilla-Reason: AssignedTo Date: Wed, 17 May 2006 15:43:56 +0000 (GMT) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=39600 Summary: A lot of connection in TIME_WAIT state on Tomcat clients Product: Tomcat 5 Version: 5.5.12 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Catalina AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: lionel.agulhon@club-internet.fr Each client connection performed on our Tomcat server is in TIME_WAIT state on client (even if the client is the Tomcat server itself). We have studied the network capture and we found an abnormal behaviour : When the client send the FIN segment, Tomcat server reply with a FIN segment instead of ACK. So the client send ACK and enter in TIME_WAIT state and it's a ugly behaviour when the client server support a hudge traffic (during a stress campaign we have reached 21000 TIME_WAIT connection !). In the TCP RFC, Closing a TCP session is always a 4 way handshake (->FIN,ACK ->,FIN ->,->Ack). you can easly reproduce : perform on the tomcat server : telnet localhost [tomcat_port] GET /toto \n\n perform : netstat -an |grep [tomcat_port] you should see a connection in TIME_WAIT State. Thanks for help, Rgds. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org