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/02/12 17:45:05 UTC

DO NOT REPLY [Bug 17010] New: - After some load HttpProcessor threads will die

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

After some load HttpProcessor threads will die

           Summary: After some load HttpProcessor threads will die
           Product: Tomcat 4
           Version: 4.0.6 Final
          Platform: HP
        OS/Version: HP-UX
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: james.kerwood@cardinal.com


After putting some stress on our web application we are getting hanging 
requests.  We used OptimizeIT to trace the threads and it seems that after a 
while we get a log4j lock (tried 1.2.5 and currently trying 1.2.7) on a rolling 
file across multiple threads. These threads then exit and sometimes the 
StandardManager exits.  When this happens our pages accept requests on port 80 
but there are no responses since the Manager is dead.
Thanks in advance for any help.
Jim Kerwood

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