You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/21 20:56:41 UTC
[jira] [Resolved] (AMQ-3718) Thread pool turnover is to heavy due
to Executor configuration
[ https://issues.apache.org/jira/browse/AMQ-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3718.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Fixed in trunk
> Thread pool turnover is to heavy due to Executor configuration
> --------------------------------------------------------------
>
> Key: AMQ-3718
> URL: https://issues.apache.org/jira/browse/AMQ-3718
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker, Connector
> Affects Versions: 5.6.0
> Environment: NA
> Reporter: Andy Gumbrecht
> Priority: Minor
> Labels: Thread
> Fix For: 5.6.0
>
> Attachments: Executors.patch, threads.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The following files use Executors that are poorly configured for every day use.
> src/main/java/org/apache/activemq/broker/BrokerService.java
> src/main/java/org/apache/activemq/thread/TaskRunnerFactory.java
> src/main/java/org/apache/activemq/transport/nio/SelectorManager.java
> Added suggested patch, but the timings should really be configurable to provide better control.
> The NIO SelectorManager change has shaved time savings of at least 1/6 - 1/4 off some of our long running tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira