From: Alejandro Pulver <alepulver_at_gmail.com>
Date: Mon, 26 Sep 2016 16:12:40 -0300

Hello,

I'm using the Grizzly 1.9 branch and would like to return an error status
code 500 when the connection thread pool is exhausted instead of failing
with an exception or ignoring the request.

For instance, an alternative to ThreadPoolExecutor$AbortPolicy that does
this. Do you have any suggestions on how to implement this?

I understand that if the connection pool is exhausted it doesn't make sense
to allocate more resources to answer all the requests with 500 but I was
thinking of only 1 thread doing that.

Thanks,
Alejandro