Looking at o.a.ajp.tc4.Ajp13Connector, I can see that curProcessors is never
decremented, which is probably what is causing this.  Unlike in the 3.3
branch, Ajp13Processor is fanatical about not dying.  I haven't looked at
the C code side, but if it is anything like the 3.3 branch, it will close
the connection to TC when the user hits the "stop" button, but in the j-t-c
branch the Processor won't die.

Before anyone's feathers get ruffled, my comparisons to 3.3 are simple
because that is the code-base I know (I've spent a great deal of time fixing
variants of 4518 on 3.3, and I still can't figure out how to fix it on
Catalina ;).
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 17, 2002 3:36 PM
Subject: DO NOT REPLY [Bug 5735] - HTTP connector running out of processors
under heavy load


> 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=5735>.
> 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=5735
>
> HTTP connector running out of processors under heavy load
>
>
>
>
>
> ------- Additional Comments From [EMAIL PROTECTED]  2002-02-17
23:36 -------
> I did a closer review of the apache access_log and the tomcat 4
catalina_log.
> When the Ajp13Connector starts spawning additional Ajp13Proccessors all of
> a sudden there is a 1:1 correlation between apache requests which get
forwarded
> to tomcat and the startup of Ajp13Processors.  Prior to the the runaway
> creation of Ajp13Processors catalina had run 2 hours without creating any
> new ones.
>
> So it looks like some bug causes existing processors to no longer be
available
> for use, and any new ones created to only be used once.
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to