Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 28 Aug 2013 14:38:52 +0000 (UTC)
From: "Hiram Chirino (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12618706.1354609865410.46946.1377700732444@arcas>
In-Reply-To: <JIRA.12618706.1354609865410@arcas>
References: <JIRA.12618706.1354609865410@arcas>
Subject: [jira] [Resolved] (AMQ-4205) Expose thread pool configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hiram Chirino resolved AMQ-4205.
--------------------------------

    Resolution: Won't Fix

Closing as wont fix.  Please re-open if can describe a use case were changing the default will improve the performance or scaling of the broker.
                
> Expose thread pool configuration
> --------------------------------
>
>                 Key: AMQ-4205
>                 URL: https://issues.apache.org/jira/browse/AMQ-4205
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker, Transport
>    Affects Versions: 5.8.0
>         Environment: NA
>            Reporter: Andy Gumbrecht
>            Priority: Minor
>              Labels: Thread, pool
>             Fix For: 5.9.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Default thread pool timeout can be too low which in turn causes excessive thread death and re-creation in AbstractInactivityMonitor.java (default 10 seconds) and TaskRunnerFactory.java (default 30 seconds).
> It would be great if these pools were configurable.
> The target to aim for is that pooled threads never die under normal load ('normal' being use case specific). 
> See http://activemq.2283324.n4.nabble.com/InactivityMonitor-Creating-too-frequent-threads-td4656752.html#a4659878

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira