DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14994 https coyote connector leaving sockets in CLOSE_WAIT [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED OS/Version|HP-UX |Linux Resolution|INVALID | Version|4.1.12 |4.1.18 ------- Additional Comments From [EMAIL PROTECTED] 2003-02-11 21:58 ------- This is actually Redhat Linux 6.2, not HP_UX. I upgraded to Tomcat 4.1.18 and it's still occurring. Andi Kleen (a developer for SuSE) says at http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.0/0053.html that it's not a OS problem if the CLOSE_WAIT's go away when I kill the process, which they do. 'netstat -apo' shows that the CLOSE_WAIT connections have no timer on them. I can reproduce the problem by: - go to any https url a browser - repeatedly click refresh very quickly in a browser Additional Log Info - Broken pipe message no longer appear with 4.1.18 - catalina message: [INFO] ThreadPool - -All threads are busy, waiting. Please increase maxThreads or check the servlet status75 75 My system: - Tomcat 4.1.18 (and 4.1.12) - Redhat Linux 6.2, kernel 2.2.19 - IBM JVM, 1.3.1 r1 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
