[
https://issues.apache.org/jira/browse/AMQ-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15098271#comment-15098271
]
Timothy Bish edited comment on AMQ-6126 at 1/14/16 3:46 PM:
------------------------------------------------------------
Add additional system properties that can be used to configure core pool size
and maximum pool size.
{noformat}
org.apache.activemq.thread.TaskRunnerFactory.corePoolSize default = 0
org.apache.activemq.thread.TaskRunnerFactory.maximumPoolSize default =
Integer.MAX_VALUE
org.apache.activemq.thread.TaskRunnerFactory.keepAliveTime default = 30
{noformat}
was (Author: tabish121):
{noformat}
org.apache.activemq.thread.TaskRunnerFactory.corePoolSize default = 0
org.apache.activemq.thread.TaskRunnerFactory.maximumPoolSize default =
Integer.MAX_VALUE
org.apache.activemq.thread.TaskRunnerFactory.keepAliveTime default = 30
{noformat}
> The corePoolSize value of the TaskRunnerFactory created Executor should be
> configurable
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-6126
> URL: https://issues.apache.org/jira/browse/AMQ-6126
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.13.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.13.1, 5.14.0
>
>
> It is currently not possible to alter the corePoolSize value of the Executor
> created in the TaskRunnerFactory in order to keep some Threads always active
> and avoid some Thread churn that might otherwise happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
