[jira] [Commented] (ARTEMIS-507) Create a new shrinking, bounded thread pool executor

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ARTEMIS-507:
---------------------------------------------------------

Commit 1591d25692c4632b18a0563442b471b000ce0100 in activemq-artemis's branch refs/heads/master from [~bgutjahr]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=1591d25 ]

ARTEMIS-507 New thread pool for client threads

- Added a thread pool executor, that combines cached and fixed size thread pooling.
  It behaves like a cached thread pool in that it reuses exising threads and removes
  idle threads after a timeout, limits the maximum number of threads in the pool, but
  queue additional request instead of rejecting them.
- changed existing code to use the new thread pool instead of a fixed-size thread pool in
  all places that are configured with a client thread pool size.


> Create a new shrinking, bounded thread pool executor
> ----------------------------------------------------
>
>                 Key: ARTEMIS-507
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-507
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Martyn Taylor
>             Fix For: 1.3.0
>
>
> The JDK ThreadPoolExecutor policies offer either a bounded thread pool executor that behaves like a fixed pool (no shrinking under periods of low/base demand), or an unbounded executor that shrinks appropriately but has potential to grow indefinitely.
> A new thread pool that takes the best of both worlds particularly for the Client Global Thread Pool would be of great benefit.



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