Jeff Mesnil created ARTEMIS-312:
-----------------------------------
Summary: Artemis clients use by default an unbounded global thread
pool
Key: ARTEMIS-312
URL: https://issues.apache.org/jira/browse/ARTEMIS-312
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 1.1.0
Reporter: Jeff Mesnil
While investigating some performance issues, we noticed that Artemis clients
(including MDBs) use by default a "global" pool by creating a cached thread
pool with 0 core pool size, Integer.MAX_VALUE max size and 60s keep alive.
This default global pool looks misconfigured. If a Artemis clients has a lot of
activity it is actually possible that threads are deleted from the pool and
added back.
Related to this, Artemis defines a threadPoolMaxSize attribute if the client is
not using a global pool. But the property does not seem to be well name.
If the Artemis client is using a "non-global" pool, this property is used to
create a newFixedThreadPool. So this property defines the actual size of the
pool, not a max size.
As a comparison, the "global" scheduled thread is instantiating with a 5 core
pool size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
