> 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 a
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
> 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:
> max
Thank you Thomas. I carefully read your explanation. It makes sense to me and
is completely different from what I understood up until this point. With this
new understanding, the problem still persists. Please let me rephrase my issues
in the light of what I just learned.
To summarize:
- thread
> Paul,
Thanks for the reply. I am not really much further with my main issue, but I
hope this reply provides more information to you, so you can either clear up my
confusion or see how tomcat doesn't work as intended in my case.
> On 5/18/21 07:44, Paul P Wolf wrote:
> >
Hi,
I am trying to run a spring boot application with an embedded tomcat. In a
scenario, where there is a lot of load on the service, I would like tomcat to
refuse connections or return something like a 503 Service Unavailable. From
what I understand, you could have this behaviour by setting ma
