Hi,
I refactored the endpoints for some of the connectors, adding the
possibility to use an Executor for the worker threads (given the accept
threads are long running threads, it does not make sense to pool them).
I would like to add a companion "Executor" element to either Engine or
Server (I haven't decided, any ideas ?) to be able to define a global
thread pool (with queuing :) ). I don't think this will be the default,
as the simple defaults are faster and probably good enough for many
cases, but in case of large servers with many thread-using services, it
could be useful to standardize on this common interface to allow sharing
the thread pool.
Note: At the moment, using the thread pool may cause memory leaks with
JMX. Also, the threads created are not thread with attributes by default
which would cause classcasts unless the executor is configured with the
appropriate thread factory. The solution might be to stop using
ThreadWithAttributes (which IMO would be logical, as in that case
threads are not used for a specified service - like a Tomcat connector -
so tracking their activity does not make sense).
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
