Great explanation, Ryan! that should go into the official Glassfish documentation; it has little or no information on this.
The default value of 5 is, imho, not good. Let's say that you have 10 clients doing file upload over slow connections (think 'mobile'). Then the time before a HTTP request is served can easily become [i]minutes[/i]. Many clients (web browsers, etc) would give up and time out. Foo!
Also, it appears that [i]each[/i] HTTP listener has its own little thread pool of 5 threads. If so, it would be [i]much[/i] better if all three Listeners (HTTP, HTTP, Admin Console) would share the same little thread pool.
Even better, it would be nice to able able to configure a specific thread pool for a certain web app (such as in my horror story).
[Message sent by forum member 'tmpsa' (per.lindberg_at_facilitylabs.com)]
http://forums.java.net/jive/thread.jspa?messageID=384042