You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/08/19 03:45:51 UTC
DO NOT REPLY [Bug 28727] -
CLOSE_WAIT connections draw 100 % cpu
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
ensorn@osti.gov changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
------- Additional Comments From ensorn@osti.gov 2004-08-19 01:45 -------
I'm experiencing something similar I believe using Tomcat 5.0.27 on an
application server that's proxied over from another (Apache) web front-end. The
application runs fine for a time, but quickly CLOSE_WAIT connections to the
Apache server start building up and the TC5 server becomes completely
non-responsive. truss-ing the Tomcat process reveals some sort of looping activity:
/88: lwp_mutex_lock(0x000EC290) (sleeping...)
/111: lwp_mutex_lock(0x000EC290) (sleeping...)
/65: lwp_cond_wait(0x0078EE88, 0x0078EE70, 0x00000000) (sleeping...)
/84: lwp_mutex_lock(0x000EC290) (sleeping...)
/9: lwp_cond_wait(0x0002D020, 0x0002D008, 0x00000000) (sleeping...)
/141: lwp_mutex_lock(0x000EC290) (sleeping...)
/25: lwp_mutex_lock(0x000EC290) (sleeping...)
/118: lwp_mutex_lock(0x000EC290) (sleeping...)
/60: lwp_cond_wait(0x00D4DDF0, 0x00D4DDD8, 0x00000000) (sleeping...)
/42: lwp_cond_wait(0x003FF4A8, 0x003FF490, 0xEE9FF7F0) (sleeping...)
/68: lwp_cond_wait(0x00791258, 0x00791240, 0xECFFF7F0) (sleeping...)
/61: lwp_cond_wait(0x00D4E4A0, 0x00D4E488, 0x00000000) (sleeping...)
/158: lwp_mutex_lock(0x000EC290) (sleeping...)
/107: lwp_mutex_lock(0x000EC290) (sleeping...)
/22: lwp_mutex_lock(0x000EC290) (sleeping...)
/112: lwp_mutex_lock(0x000EC290) (sleeping...)
/71: lwp_mutex_lock(0x000EC290) (sleeping...)
/183: lwp_mutex_lock(0x000EC290) (sleeping...)
/54: lwp_cond_wait(0x0045D220, 0x0045D208, 0x00000000) (sleeping...)
/16: lwp_mutex_lock(0x000EC290) (sleeping...)
/144: lwp_mutex_lock(0x000EC290) (sleeping...)
/114: lwp_mutex_lock(0x000EC290) (sleeping...)
/23: lwp_mutex_lock(0x000EC290) (sleeping...)
followed by many lines of :
/10: poll(0xF98FFD58, 0, 50) = 0
/2: lwp_cond_wait(0x0002CB80, 0x0002CB68, 0xFC77FD30) Err#62 ETIME
During this time, Tomcat is apparently sleeping, and completely non-responsive.
A restart results in the server responding again for a short time, then going
back into the same state.
Apache 1.3.27 on web server, using ProxyPass to the application server, Solaris
9 OS, JVM 1.4.2_04. Tomcat version 5.0.27. Any pointers would be appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org