CherryPy wsgiserver should reject conns when Queue.Full

Originally reported by: Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco)

---

In 49b22a7, CherryPy 3.0 was updated to reject connections when Queue.Full. This change did not make it into 3.2.x. It should be ported forward.

---

• Bitbucket: https://bitbucket.org/cherrypy/cherrypy/issue/1301

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

Porting forward look challenging. The codebase has changed a lot. Also, the new server object has attributes that may or may not be related. For instance, Server.socket_timeout, Server.socket_queue_size, and Server.thread_pool_max seem related. However, there doesn't appear to be any handling of Queue.Full.

@Fumanchu Do you have any hints about what is the right thing to do here?

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

I'd like to offer a $200 bounty to implement a robust fix for this issue if implemented against CherryPy 3.2.x.

Original comment by James Rydberg (Bitbucket: jamesrydberg, GitHub: jamesrydberg):

---

Original comment by Allan Crooks (Bitbucket: the_allanc, GitHub: Unknown):

---

Reimplementation of code to allow bounded request queues - rejecting requests when the queue is full. Fixes #1301.

Original comment by Allan Crooks (Bitbucket: the_allanc, GitHub: Unknown):

---

I've tested this with Python 2 and 3, and appears to work. I've branched this off the CP3.3 development branch, but it can be easily transplanted against CP3.2.

Original comment by Jason R. Coombs (Bitbucket: jaraco, GitHub: jaraco):

---

woo! Would you like bitcoin or paypal?

Original comment by Gustavo Picon (Bitbucket: tabo, GitHub: tabo):

---

Reimplementation of code to allow bounded request queues - rejecting requests when the queue is full. Fixes #1301.