DO NOT REPLY [Bug 28727] - CLOSE_WAIT connections draw 100 % cpu

[bu...@apache.org]

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





------- Additional Comments From aquilino@dreamteam.it  2004-10-06 16:02 -------
I can confirm this bug on jakarta-tomcat-5.0.28-embed on Solaris 2.8


Here are my suggestions to reproduce it:

- start Tomcat on server S

- monitor the status of connections on server S
while(1)
netstat -a|grep CLOSE_WAIT|wc -l
sleep 5
end

- establish more than 500 concurrent HTTP connections from client C
(We used JMeter to run a work job with 500 threads, 5 requests each)

- DETACH THE NETWORK CABLE on client C
when you are sure the server is managing at least 500 connections from C

- ATTACH THE NETWORK CABLE on client C

Expected result:
Connections in CLOSE_WAIT status get closed gracefully on server S.

Actual Result:
Connections in CLOSE_WAIT status never get closed on server S.
If you connect to the Tomcat server, response time is very slow.
The number of connections in CLOSE_WAIT status keeps growing.


Thanks for your time and efforts

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org