DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=39600>. 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: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
