Currently the AbstractNIOConnPool is capable to handle timeouts for en-queued requests (requests added in leasingRequests connection).
What AbstractNIOConnPool - deal with slow connections, that already are open and being executed. Slow connections are connections that are not completed withing some request processing timeout.
Example. Consider a specific case, when a remote server holds a connection open, but transmits information slowly (e.g. 8 bytes in each 100ms). In application under the high load it means that we would stuck with no free connections to process new requests for a long period of time.
In such cases, as a developer I want to specify time in which we would close current open connection, even if it is already processing the data.