activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Huang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-5480) Provider fine-grained control for SelectorManager's threadpool
Date Fri, 12 Dec 2014 06:45:13 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243788#comment-14243788
] 

Benjamin  Huang edited comment on AMQ-5480 at 12/12/14 6:44 AM:
----------------------------------------------------------------

Reopen as tuning options on reject policy are desired


was (Author: benjaminhuang):
Reopen as tuning options are desired

> 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)

Mime
View raw message