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

2016-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 --- Comment #8 from Remy Maucherat --- That's a useful clarification actually, the standard executor is not an ExecutorService, there's another thread pool in there that is an ExecutorService. It is likely I'll adjust the

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

2016-06-04 Thread bugzilla
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

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

2016-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 --- Comment #6 from Remy Maucherat --- So you're saying effectively that the NIO2 connector would be better off if it used *two* separate executors: one ExecutorService internally (NIO2 needs one), and an external executor.

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

2016-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 --- Comment #5 from Ravi Sanwal --- Typo in previous comment. It should be. We should at lease fix the connector documentation for this behavior and explain that it is better to not use an external executor *but* an

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

2016-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 --- Comment #4 from Ravi Sanwal --- Can it at least give the user some control put a cap on the number of threads? May be I am not explaining my problem correctly. Regardless. Tomcat NIO2 connector still doesn't follow the

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

2016-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 Remy Maucherat changed: What|Removed |Added Severity|normal |enhancement

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

2016-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 Ravi Sanwal changed: What|Removed |Added Resolution|INVALID |---

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

2016-06-01 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59650 Remy Maucherat changed: What|Removed |Added Status|NEW |RESOLVED