tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 59650] NIO2 connector does not respect executor bounds, reuses NIO.2 threads for processing request on connections
Date Fri, 03 Jun 2016 22:38:24 GMT

--- 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. And most processing will need to be executed twice on
two different executors. Since I didn't think the behavior would be useful, I
wrapped the executor assuming it is an ExceutorService (the thread pool Tomcat
provides that is the standard implementation for the Executor element is one)
since that is the most efficient solution.

It is open source, you can submit a patch but I'm quite skeptical. It would
have to use a master flag (most likely the internalExecutor flag can work).

I would instead recommend trying to use a pool that implements ExecutorService,
it looks to me like a useful interface for thread management.

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message