I have the following question on Tomcat's acceptCount
.
It says:
The maximum queue length for incoming connection requests when all possible request processing threads are in use. Any requests received when the queue is full will be refused. The default value is 10.
I am not sure how this works. I mean I know that there is a separate TCP queue that determines how many connections can come so if I put acceptCount
in application level e.g. 30000, does it make any difference?
I mean it seems that this configuration is not useful.
Am I right?
The default installation of Tomcat sets the maximum number of HTTP servicing threads at 200. Effectively, this means that the system can handle a maximum of 200 simultaneous HTTP requests.
2.10 Using Tomcat connectionTimeout Attribute to Defend Against Denial-of-Service Attack. If a client sends a request in chunks, the server keeps waiting until the complete request is received.
If Tomcat does not swallow the body the client is unlikely to see the response. If not specified the default of 2097152 (2 megabytes) will be used. A value of less than zero indicates that no limit should be enforced.
There are two basic Connector types available in Tomcat - HTTP and AJP.
This is a direct pass-through to the backlog
parameter of ServerSocket's constructor. The idea is that the OS can hold onto incoming connections even if they can't be processed right away. It's only useful if you have bursty traffic and fast processing times.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With