[
https://issues.apache.org/jira/browse/AMQ-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5480.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.11.0
Assignee: Timothy Bish
Add simillar options for corePoolSize and maximumPoolSize to the selector
manager.
> 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)
