activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-6139) Unable to config maxThreadPoolSize in broker
Date Fri, 22 Jan 2016 22:59:39 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-6139.
-----------------------------
       Resolution: Duplicate
         Assignee: Timothy Bish
    Fix Version/s: 5.14.0
                   5.13.1

These values have already been updated to be configurable, check the latest source for the
TaskRunnerFactory.  

> Unable to config maxThreadPoolSize in broker
> --------------------------------------------
>
>                 Key: AMQ-6139
>                 URL: https://issues.apache.org/jira/browse/AMQ-6139
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: activemq-pool
>    Affects Versions: 5.11.1
>            Reporter: JIE CHEN
>            Assignee: Timothy Bish
>            Priority: Critical
>             Fix For: 5.13.1, 5.14.0
>
>
> The default value of maxThreadPoolSize is Integer.MAX_VALUE in TaskRunnerFactory for
broker service, which does not make any sense. If you set -Dorg.apache.activemq.UseDedicatedTaskRunner=false
but you are still able to create as many threads as you want. Suggest to make this configurable
to limit the threads number the ActiveMQ broker can create.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message