Paul,
On 5/19/21 08:32, Paul P Wolf wrote:
sorry, my message was misformated, so here again with hopefully better
formatting:
The clients timeout because they spend more than timeout in the
acceptCount/backlog queue waiting for Tomcat to call Socket.accept()
Ok, so you are stating, that
On 20/05/2021 10:58, Mark Thomas wrote:
I'll get docs updated. The website will update after the next round of
releases (due in the first week or so of June).
https://ci.apache.org/projects/tomcat/tomcat10/docs/config/http.html
Mark
On 20/05/2021 07:24, Paul P Wolf wrote:
OK, that looks like clients with a connection timeout of 5s.
Correct. I think I forgot to mention, that I set the connection timeout of the
curl instances to 5s. I didn't set the max timeout
Connection refusal is entirely under the control of the OS
> OK, that looks like clients with a connection timeout of 5s.
Correct. I think I forgot to mention, that I set the connection timeout of the
curl instances to 5s. I didn't set the max timeout
> >> Connection refusal is entirely under the control of the OS and will
> >> be driven largely by the
On 19/05/2021 13:32, Paul P Wolf wrote:
So we have:
maxThreads=4
maxConnections=10
acceptCount=20
The processing time of each request is 10s (thanks to a 10s sleep, which blocks
the Thread).
So here is what I see instead (note I don't guess the response time, but do
actually
sorry, my message was misformated, so here again with hopefully better
formatting:
> The clients timeout because they spend more than timeout in the
> acceptCount/backlog queue waiting for Tomcat to call Socket.accept()
Ok, so you are stating, that clients timeout while their requests are in
> The clients timeout because they spend more than timeout in the
> acceptCount/backlog queue waiting for Tomcat to call Socket.accept()
Ok, so you are stating, that clients timeout while their requests are in the
acceptCount/backlog. This is not what I am seeing. See below.
> So we have:
>
