If you're talking about the non-native AJP connector, then this is a
long-standing issue.
acceptCount is essentially ignored in this case and all concurrent
requests above pool size /minus 2/ go off into limbo and are not handled
properly. I don't understand the off-by-2 error, but it is clea
Timir Hazarika wrote:
Andre,
Response from Leon just about summarizes this issue: the shock absorber you
mention is not configurable. Setting the acceptCount to 1 or nine hundred
produces exactly the same behavior in terms of connections awaiting
response.
Then that would be a bug, no ? In the
Andre,
Response from Leon just about summarizes this issue: the shock absorber you
mention is not configurable. Setting the acceptCount to 1 or nine hundred
produces exactly the same behavior in terms of connections awaiting
response.
The "stricter" scheme hence, serves as a usable application wo
Timir Hazarika wrote:
This is not an accept problem, this is a problem with having serviced a
request via a socket and then closing the connection. Given that you
can't avoid accepting connections on a useful web server, you will not
be able to prevent them from going through their natural l
>
>
> This is not an accept problem, this is a problem with having serviced a
request via a socket and then closing the connection. Given that you
can't avoid accepting connections on a useful web server, you will not
be able to prevent them from going through their natural lifecycle.
>
Chris,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timir,
On 4/9/2010 8:10 AM, Timir Hazarika wrote:
> Mark, I'm using netstat as follows. You can see the tomcat process listening
> on 8443 and all the incoming requests in TIME_WAIT. These connections do get
> cleared after the default timeout of 60 s
My point exactly. Is there an alternative setting that I may use ?
Timir
On Fri, Apr 9, 2010 at 5:47 PM, Leon Rosenberg <
rosenberg.l...@googlemail.com> wrote:
> I remember a more or less public discussion some time ago, that the
> acceptCount setting is virtually worthless, because modern kerne
I remember a more or less public discussion some time ago, that the
acceptCount setting is virtually worthless, because modern kernels
simply ignore it.
Leon
P.S. By ignore I mean that ServerSocket.accept(100) has no effect.
On Fri, Apr 9, 2010 at 2:10 PM, Timir Hazarika wrote:
> Mark, I'm usin
Mark, I'm using netstat as follows. You can see the tomcat process listening
on 8443 and all the incoming requests in TIME_WAIT. These connections do get
cleared after the default timeout of 60 seconds, my intention is to refuse
creating them in the first place.
netstat -anp | grep 8443
tcp
On 09/04/2010 10:55, Timir Hazarika wrote:
Chuck, this is the same configuration as in my initial question, except for
the value of accept count. I've already tried setting it to zero as well :
Folks,
What is the best way to limit connections in tomcat, if there is one ? I
have tried acceptCou
Chuck, this is the same configuration as in my initial question, except for
the value of accept count. I've already tried setting it to zero as well :
Folks,
What is the best way to limit connections in tomcat, if there is one ? I
> have tried acceptCount, maxThreads, even specifying explicit exe
On Apr 8, 2010, at 13:37, "Timir Hazarika"
wrote:
> How would this configuration look like in server.xml ?
- Chuck
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...
You just lost me. How would this configuration look like in server.xml ?
Timir
On Thu, Apr 8, 2010 at 9:09 PM, Caldarale, Charles R <
chuck.caldar...@unisys.com> wrote:
> > From: Timir Hazarika [mailto:timir.hazar...@gmail.com]
> > Subject: Re: Tomcat does not honor acceptC
> From: Timir Hazarika [mailto:timir.hazar...@gmail.com]
> Subject: Re: Tomcat does not honor acceptCount configuration variable
>
> I would like tomcat to use a maximum of (say) 5 sockets on my system.
> Further connection requests should be dropped. How may I achieve that ?
Th
Chuck,
I would like tomcat to use a maximum of (say) 5 sockets on my system.
Further connection requests should be dropped. How may I achieve that ?
> The acceptCount is the value used by the platform's TCP/IP stack
> to limit the number of HTTP connection requests held in a queue.
> The number a
> From: Timir Hazarika [mailto:timir.hazar...@gmail.com]
> Subject: Tomcat does not honor acceptCount configuration variable
>
> What is the best way to limit connections in tomcat, if there is one ?
Somewhat depends on what you think "connection" means. If you're actually
referring to sessions
16 matches
Mail list logo
