tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Nielsen <gl...@voyager.apg.more.net>
Subject Re: DO NOT REPLY [Bug 5735] - HTTP connector running out of processors under heavy load
Date Mon, 18 Feb 2002 15:42:02 GMT
I have setup a test environment to try and reproduce the problem.

It is using the same Tomcat server but a different Apache server.
I have debug turned on in Tomcat for the AJP connector and debug
turned on for mod_jk in Apache.

One problem I am encountering when trying to test with debug is
that debug logging adds alot of overhead.

The load testing has generated enough request's to cause 26 
Ajp13Processors to be created at this point.  But the server
load is a problem.  Load on the Tomcat server is 4.5 (Sun 250
with 1 CPU) and the load on the Apache server is 1.8 (Sun Netra T1
with 1 CPU).

Now it is just a matter of waiting and see if it fails 2-3 hours
into the test.

Regards,

Glenn

Glenn Nielsen wrote:
> 
> Kevin Seguin wrote:
> >
> > >
> > > ------- Additional Comments From glenn@apache.org  2002-02-18
> > > 00:30 -------
> > > Based on the apache logs it looks like when the
> > > Ajp13Processor's become
> > > unavailable for reuse they have successfully handled a request.  I can
> > > tell this due to entries existing in the apache access_log
> > > for image files,
> > > etc. related to a request forwarded to Tomcat via mod_jk
> > > being requested.
> > >
> > > So the problem which is causing the Ajp13Processor's to hang
> > > must be in
> > > Ajp13Proccessor code after a request has been handled and
> > > before it calls
> > > connector.recycle(this) to make itself available to process
> > > another Ajp request.
> > >
> >
> > that would be somewhere in Ajp13Processor.process()...
> >
> > if you can reproduce this consistently, can you turn up the logging for the ajp13
connector, then send me (seguin at apache.org) the all of the pertinent log files and the
captured stdout/stderr - unfortunately, some of the ajp stuff "logs" to stdout :( - from a
run where this problem occurs?
> >
> 
> I ran across this AJP problem when trying to put a new site into production.
> And it did happen consistently, about 2 - 2 1/2 hours after Tomcat was started.
> But I didn't have time during the window for replacing the old site with the
> new to do a run with debug on.  I will have to see if I can setup a test
> environment that can duplicate the problem.
> 
> I'll see what I can do.
> 
> Glenn
> 
> ----------------------------------------------------------------------
> Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> MOREnet System Programming               |  * if iz ina coment.      |
> Missouri Research and Education Network  |  */                       |
> ----------------------------------------------------------------------
> 
> --
> To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

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


Mime
View raw message