Tomcat acceptCount

[peterdnight]

Enhancement:
Add additional tomcat parameter: accept-count. This is incredibly useful parameter when implementing throttles to protect resources from heavy activity spikes. It is the best friend of max-threads which is already supported. Otherwise you end up with hundreds of sockets sitting in blocked state, rather then sending a 503 - try again later.

server:
  port: 8080
  tomcat:
    max-threads: 10
    accept-count: notImplemented

[cabbonizio]

+1

[peterdnight]

I had some time to do more digging through the boot classes - and testing - that the following is required to effectively manage queued connections.

This does work - and is a brute force way of managing resources. eg. Browsers will get a not available message, rest clients will hopefully wait 60s*random and retry.

org.springframework.boot.autoconfigure.web.ServerProperties line 807:
...
                        protocol.setMaxThreads(Tomcat.this.maxThreads);
need to add:

                        protocol.setMaxConnections(Tomcat.this.maxConnections);
                        protocol.setBacklog(Tomcat.this.acceptCount);

[isopov]

To be more general - is there any difference with Jetty's "acceptQueueSize" option? If it is the same - maybe it should be supported with same spring-boot config?

http://wiki.eclipse.org/Jetty/Howto/Configure_Connectors

[snicoll]

duplicates #6571