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=28727>. 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=28727 CLOSE_WAIT connections draw 100 % cpu Summary: CLOSE_WAIT connections draw 100 % cpu Product: Tomcat 5 Version: 5.0.19 Platform: PC OS/Version: Windows XP Status: NEW Severity: Blocker Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] We use Tomcat 5.018/5.0.19 in a mission critical application. Every second or third try specific connections fail. Tomcat then seems to be unable to close the connections, although the client already has terminated its session (and shutdown his computer). Within Tomcat the connections are left as "CLOSE_WAIT". (=> netstat -a) As soon as one connection shows up as "CLOSE_WAIT", the connection-thread begins to loop (seems as if select is no more blocking) and starts to eat up cpu power. When two or three threads are in the state "CLOSE_WAIT", Tomcat performance slows down until the non-blocking "CLOSE_WAIT"-threads are consuming everything. We have to shutdown Tomcat then. What is happening here? Is there a workaround available? What about the CLOSE- WAIT-connections (they are all issued via mobile clients via GPRS) We tried both Tomcat 5.0.19 and 5.0.18. Same situation. Environment: Windows 2000/XP, Service Packs applied; Apache 2.0.47, Mode_JK2, JDK1.4.2_03 and JDK 1.4.2_04 (tried both, both SUN) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
