Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C294C19DDB for ; Fri, 15 Apr 2016 06:06:25 +0000 (UTC) Received: (qmail 91443 invoked by uid 500); 15 Apr 2016 06:06:25 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 91404 invoked by uid 500); 15 Apr 2016 06:06:25 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 91395 invoked by uid 99); 15 Apr 2016 06:06:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Apr 2016 06:06:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7C5872C1F61 for ; Fri, 15 Apr 2016 06:06:25 +0000 (UTC) Date: Fri, 15 Apr 2016 06:06:25 +0000 (UTC) From: "Bernd Gutjahr (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ARTEMIS-485) Global client thread pool is not unbounded by default MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Bernd Gutjahr created ARTEMIS-485: ------------------------------------- Summary: 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 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)