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: 30 Jul 2003 03:24:49 -0000
Message-ID: <20030730032449.27290.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 21983]  -
    Coyote JK2 connector ignores Accept count property

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

Coyote JK2 connector ignores Accept count property

william.barker@wilshire.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Major                       |Minor


------- Additional Comments From william.barker@wilshire.com  2003-07-30 03:24 -------
Yes, it should allow you to set the acceptCount.  However, the benefit of doing 
so is really really tiny.  (I'm assuming the pre-fork MPM, because it is easier 
to explain:  the other MPMs work similarly however.)  What happens is that each 
Apache child is connected to a single Tomcat thread.  When the Tomcat thread 
finishes the request, it won't go back to the ServerSocket:  It will wait until 
it's Apache child sends it another request.  The only thing that the 
acceptCount would help is the case where Apache suddenly needs to create a 
large number of new children (and even then, you'd probably need a pretty beefy 
box to see a failure).

For what you want, you need to configure the "backlog" in Apache.

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