You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/09/17 16:46:05 UTC
[jira] [Commented] (QPID-6741) ThreadPoolExecutors used for virtual
host IO / port IO do not scale above minimum pool size
[ https://issues.apache.org/jira/browse/QPID-6741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14803008#comment-14803008 ]
ASF subversion and git services commented on QPID-6741:
-------------------------------------------------------
Commit 1703636 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1703636 ]
QPID-6741: [Java Broker] Make NCS scale the number of connections in the pool until pool size reaches the maximum
* Also set connection timeout to 1h for all threads.
Note that core pool size will currently not shrink.
> ThreadPoolExecutors used for virtual host IO / port IO do not scale above minimum pool size
> -------------------------------------------------------------------------------------------
>
> Key: QPID-6741
> URL: https://issues.apache.org/jira/browse/QPID-6741
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0
> Reporter: Keith Wall
> Fix For: qpid-java-6.0
>
>
> NetworkConnectionScheduler uses a {{java.util.concurrent.ThreadPoolExecutor}} to service AMQP IO. The intention is that the executor will dynamically scale the number of threads in the pool as load increases until a maximum is reached and then at that point requests will be queue. However, TPE, out of the box, does not offer such behaviour. When used with a unbounded queue, TPE will *never* increase the threads beyond the core size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org