Writing scalable server applications in the Java™ programming language has always been difficult. Before the advent of the Java New I/O API (NIO), thread management issues made it impossible for a server to scale to thousands of users. The Grizzly NIO framework has been designed to help developers to take advantage of the Java™ NIO API.
Is there a way to monitor number of active selectors? Is there a indicator that selectors are running close to the limit?
Strategy: SameThreadIOStrategy Grizzly version: org.glassfish.grizzly:grizzly-framework:2.3.28