Salut,
Sahoo wrote:
> Jan,
>
> I was under the impression that web requests are handled by threads from
> thread-pools configured in domain.xml under <thread-pools> element, but
> I observed something else earlier today. I saw web requests were handled
> by threads that created using JDK's thread pool facility. Any reason why
> we don't use appserver thread pool? When did we stop using it?
we never used this element for Grizzly/WebContainer. Grizzly always used
its own thread pool (called Pipeline). V3 (with the integration of
Grizzly 1.9.0) recently started to use the ExecutorServices API from the
JDK. Maybe you have looked at v3?
Thanks
-- Jeanfrancois
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>