users@glassfish.java.net

Re: Which thread pools in GlassFish v2 should be optimized in order to

From: <glassfish_at_javadesktop.org>
Date: Sat, 17 Nov 2007 20:18:32 PST

I agree, this could have been better. For this setting, see: Configuration> HTTP Service and
click on RequestProcessing tab. Frankly, it should have been named "Request Processing".

You'll see the settings with initial count of http-request-processing threads being 2. These threads
are named: httpWorkerThread-<listener-port>-<id-from-0->n>.

Note that when you modify this, the request processing threads for [b]all [/b] http-listeners
are modified. Thus, if you set above value as 5, you'll have 15 initial threads (as we have 3
listeners, by default -- http-listener-1, http-listener-2 and admin-listener) [b] to begin with [/b].
Let's call it the Grizzly-Thread-Pool.

Read blogs from Scott Oaks and Jeanfrancois Arcand before modifying these values as
increasing the number of threads in Grizzly-Thread-Pool is not necessarily a good thing.

Regards,
Kedar
[Message sent by forum member 'km' (km)]

http://forums.java.net/jive/thread.jspa?messageID=245944