Apache webserver - What happens to requests, when all worker threads are busy

Question

As far as I researched, the scenario when all worker threads are busy serving requests, what happens to the requests that comes next.

1. Do they wait?
2. Is this related to some configurable parameters?
3. Can I get the count of such requests ?

Adding to this please can you explain or give a link where I can get a clear picture of request processing strategy of Apache webserver?

Thanks for Looking at!!

Answer 1

This answer is given in 2015. So I talk about apache httpd 2.4.

1. They wait because the connection is queued on the TCP socket (the connection is not ACKed) Although the default length of the backlog may be set way too high on linux boxes. This may result in connections being closed due to kernel limits being in place.
2. ListenBacklog (with caveats. See 1.)
3. This is described here. With lots of interesting stuff.

Read through Apache TCP Backlog by Ryan Frantz to get the glory details about the Apache backlog.

Answer 2

When all Apache worker threads are busy, the new request is stalled (it waits) until one of those worker threads is available. If the client gives up waiting, or you surpass the maximum wait time in your configuration file; it will drop the connection.