[Bug 59650] NIO2 connector does not respect executor bounds, reuses NIO.2 threads for processing request on connections

https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 --- Comment #7 from Ravi Sanwal --- I partly understand what you said. AND as I mentioned in my previous comment about the workaround, there is a way out. Your statement, however, about the tomcat standard executor being an ExecutorService (for

[GUMP@vmgump]: Project tomcat-trunk-test-nio (in module tomcat-trunk) failed

-commons/daemon/dist/bin/commons-daemon-20160604-native-src.tar.gz -Dexamples.sources.skip=true -Dbase.path=/srv/gump/public/workspace/tomcat-trunk/tomcat-build-libs -Djdt.jar=/srv/gump/packages/eclipse/plugins/R-4.5-201506032000/ecj-4.5.jar -Dtest.relaxTiming=true -Dcommons-daemon.jar=/srv/g

[GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed

ump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-20160604.jar:/srv/gump/packages/commons-collections3/commons-collections-3.2.1.jar:/srv/gump/public/workspace/apache-commons/cli/target/commons-cli-1.4-SNAPSHOT.jar:/srv/gump/public/workspace/commons-lang-trunk/target/commons-la