Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: 2 Feb 2002 22:39:22 -0000
Message-ID: <20020202223922.5312.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
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 remm@apache.org  2002-02-02 22:39 -------
I think I found an explanation for at least part of the bug.

Looking at the algorithm, it's very possible that it would use more processors
(usually, no more than one or two) than active clients under very high loads,
because there's a amount of time (very small, but not null) between the instant
the client is disconnected after the response is finished, and the instant where
the processor has finished being recycled and is ready to process requests again.
This behavior won't be fixed.

OTOH, I have never seen the connector completely misbehave, run out of
processors and die. If you have experienced it, and can help me reproduce it,
I'd like to hear from you. Of course, if you can come up with a fix, that would
be awesome :)

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