activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARTEMIS-485) Global client thread pool is not unbounded by default
Date Tue, 26 Apr 2016 15:26:12 GMT

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

Justin Bertram resolved ARTEMIS-485.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

>From what I can tell this issue has been resolved.  If not, please re-open with details
of what still needs to be completed.

> Global client thread pool is not unbounded by default
> -----------------------------------------------------
>
>                 Key: ARTEMIS-485
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-485
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Bernd Gutjahr
>             Fix For: 1.3.0
>
>
> With the change #263, "Allow configurable size for client global pools", the default
global client thread pool has been changed from an unbounded thread pool to a fixed size pool.
In addition, that changed made it impossible to configure the thread pool as unbounded.
> With the unbounded thread pools, client threads are created on demand, but get cleared
after an idle time of one minute. In normal client operations, there weren't many client threads.
With the change to a fixed size thread pool, the pool quickly fills up with the configured
number of client threads, which never go away.
> I have seen that each thread had ~500kB allocated, which leads to 250MB  with the default
of 500 threads.
> Therefore, I would like to have the default changed back to -1 (= unbounded thread pool),
as it also documented in the "Client-Side Thread Management" chapter of the user documentation.
The code also needs to be fixed to handle -1 correctly, as it currently changes it to 2.



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

Mime
View raw message