Use standard blocking reads and writes.
Use standard blocking reads and writes.
This is more CPU efficient per request than NonBlockingServletIo, but is likely to require a larger request thread pool for the same load.
Use non-blocking reads and writes.
Use non-blocking reads and writes. Available only on containers that support Servlet 3.1.
This can support more concurrent connections on a smaller request thread pool than BlockingServletIO, but consumes more CPU per request. It is also known to cause IllegalStateExceptions in the logs under high load up through at least Tomcat 8.0.15. These appear to be harmless, but are operationally annoying.
Determines the mode of I/O used for reading request bodies and writing response bodies.