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 2F4F718B71 for ; Wed, 9 Dec 2015 20:21:12 +0000 (UTC) Received: (qmail 5273 invoked by uid 500); 9 Dec 2015 20:21:11 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 5150 invoked by uid 500); 9 Dec 2015 20:21:11 -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 5124 invoked by uid 99); 9 Dec 2015 20:21:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Dec 2015 20:21:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id EE79E2C14F7 for ; Wed, 9 Dec 2015 20:21:10 +0000 (UTC) Date: Wed, 9 Dec 2015 20:21:10 +0000 (UTC) From: "Justin Bertram (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (ARTEMIS-312) Artemis clients use by default an unbounded global thread pool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARTEMIS-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Bertram reassigned ARTEMIS-312: -------------------------------------- Assignee: Justin Bertram > Artemis clients use by default an unbounded global thread pool > -------------------------------------------------------------- > > Key: ARTEMIS-312 > URL: https://issues.apache.org/jira/browse/ARTEMIS-312 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker > Affects Versions: 1.1.0 > Reporter: Jeff Mesnil > Assignee: Justin Bertram > > While investigating some performance issues, we noticed that Artemis clients (including MDBs) use by default a "global" pool by creating a cached thread pool with 0 core pool size, Integer.MAX_VALUE max size and 60s keep alive. > This default global pool looks misconfigured. If a Artemis clients has a lot of activity it is actually possible that threads are deleted from the pool and added back. > Related to this, Artemis defines a threadPoolMaxSize attribute if the client is not using a global pool. But the property does not seem to be well name. > If the Artemis client is using a "non-global" pool, this property is used to create a newFixedThreadPool. So this property defines the actual size of the pool, not a max size. > As a comparison, the "global" scheduled thread is instantiating with a 5 core pool size. -- This message was sent by Atlassian JIRA (v6.3.4#6332)