In my testing I was never able to create an executor for JBoss Web that didn't have dismal performance. Since TorqueBox needs to be able to easily control the maximum number of http threads we've written a simple service that reads a system property and sets the http connector's protocol handler's maxThreads. This works great and doesn't incur the performance hit of using a separate executor. If there's interest, we could submit a patch upstream to accept a max-threads attribute on the connector definitions.

Ben

On Oct 20, 2011, at 12:15 PM, Andrig Miller wrote:

One thing that I have found with playing around with the various subsystems, is JBoss Web. JBoss Web doesn't expose a thread pool configuration, just a single attribute called max-connections. It also then has an "executor" attribute, which just takes a thread pool name from the JBoss Threads configuration.

So, this one is inconsistent with the other subsystems, and I'm not sure if it should be changed to be consistent or not, since the default doesn't use JBoss Threads. This would also complicate any "global" view in the console.

Andy