I remember a more or less public discussion some time ago, that the acceptCount setting is virtually worthless, because modern kernels simply ignore it.
Leon P.S. By ignore I mean that ServerSocket.accept(100) has no effect. On Fri, Apr 9, 2010 at 2:10 PM, Timir Hazarika <timir.hazar...@gmail.com> wrote: > Mark, I'm using netstat as follows. You can see the tomcat process listening > on 8443 and all the incoming requests in TIME_WAIT. These connections do get > cleared after the default timeout of 60 seconds, my intention is to refuse > creating them in the first place. > > netstat -anp | grep 8443 > > tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN > 15450/java > tcp 0 0 10.64.62.101:8443 72.163.140.73:19735 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19744 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19746 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19730 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19745 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19732 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19737 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19742 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19733 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19741 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19747 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19740 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19731 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19743 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19734 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19736 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19738 > TIME_WAIT - > tcp 0 0 10.64.62.101:8443 72.163.140.73:19739 > TIME_WAIT - > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
