You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2016/02/26 11:27:18 UTC
[jira] [Commented] (AMQ-5480) Provider fine-grained control for
SelectorManager's threadpool
[ https://issues.apache.org/jira/browse/AMQ-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168786#comment-15168786 ]
Dejan Bosanac commented on AMQ-5480:
------------------------------------
There's some more work done in this area here [AMQ-6184].
> Provider fine-grained control for SelectorManager's threadpool
> --------------------------------------------------------------
>
> Key: AMQ-5480
> URL: https://issues.apache.org/jira/browse/AMQ-5480
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Selector
> Affects Versions: 5.9.0
> Environment: UbuntuServer 12.04 x86_64, ActiveMQ-5,9.1, E5-2620 v2 @2.10GHz, 64GB RAM
> Reporter: Benjamin Huang
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.11.0
>
>
> In SelectorManager::createDefaultExecutor, the ThreadPoolExecutor is created with Integer.MAX_VALUE as MaximumPoolSize. This does not work well under our scenarios. It would be nicer to give fine-control over CorePoolSize, MaximumPoolSize as what's been done for KeepAlive Time
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)