>Can somebody shed some light on this?
>IMO some arbitrary thread pool should not be used by jboss web.
What about a dedicated executor like this ?
<bounded-queue-thread-pool name="webserver" blocking="true" allow-core-timeout="false">
<core-threads count="10" per-cpu="20"/>
<queue-length count="10" per-cpu="20"/>
<max-threads count="10" per-cpu="20"/>
<keepalive-time time="10" unit="SECONDS"/>
</bounded-queue-thread-pool>
<connector enable-lookups="false" enabled="true" executor="webserver" .... />
By the way, what does the max-connections attribute of the connector stands for ? Apparentely it seems the equivalent of the older MaxThreads.....it might be a little misleading....
Can somebody shed some light on this?
On May 20, 2011, at 7:12 PM, Andrig Miller wrote:
>> so you say one of them is for http connector ?
>
> I have been changing the jca-short-running bounded-queue-thread-pool, and based on looking at the information in JConsole, it is being used by JBoss Web.
IMO some arbitrary thread pool should not be used by jboss web.
I would suggest either a custom (properly named) one.
Ike
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev