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/03/21 18:42:06 UTC

DO NOT REPLY [Bug 18229] New: - "All threads are busy, waiting." resource leak bug?

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

"All threads are busy, waiting." resource leak bug?

           Summary: "All threads are busy, waiting." resource leak bug?
           Product: Tomcat 4
           Version: 4.1.18
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: jemiller@uchicago.edu


I've received the following error message twice now.

INFO: All threads are busy, waiting. Please increase maxThreads or check the 
servlet status75 75

I'm running Tomcat 4.1.18 in stand-alone mode with only the HTTPS port enabled 
on Solaris 8 with J2SE 1.4.1_01. I noticed that several other users on the 
tomcat-user list have reported the same error and I'm wondering if there is 
some kind of resource leak in Tomcat 4.1.18.

I never had this problem with older versions of Tomcat. My application isn't 
very heavily used.

Jon

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