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 2003/07/11 21:03:14 UTC

DO NOT REPLY [Bug 21524] New: - Thread Leak

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=21524>.
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=21524

Thread Leak

           Summary: Thread Leak
           Product: Tomcat 4
           Version: 4.1.24
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: rishi@quantal.com


I have isolated this problem in the CoyoteConnector thread pooling. Upon every 
HTTP request the thread count goes up and never gets cleaned by the GC. I am 
able to monitor this through the windows task manager (added thread count 
column). Tomcat initially starts with 45 threads; let the server run for 24 
hours (about 70 to 80 HTTP requests) and the thread count is > 230. This 
eventually results in server crash when the VM runs out of heap. Thread pool 
configuration is ...minProcessors="5" maxProcessors="25 acceptCount="10 
enableLookups="false". Increasing JMV memory only delays the crash. This is 
turning out to be a serious problem in our production servers. Is there is work 
around? Server is running on windows-2000 SP3. Java version is 1.3.1_04-b02.

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