Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7EF3E973 for ; Wed, 28 Nov 2012 10:03:16 +0000 (UTC) Received: (qmail 67769 invoked by uid 500); 28 Nov 2012 10:03:16 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 67590 invoked by uid 500); 28 Nov 2012 10:03:16 -0000 Mailing-List: contact dev-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 dev@activemq.apache.org Received: (qmail 67251 invoked by uid 99); 28 Nov 2012 10:03:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 10:03:14 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.250.139 is neither permitted nor denied by domain of andy.gumbrecht@orprovision.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 10:03:09 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TdeTg-0008LA-Rq for dev@activemq.apache.org; Wed, 28 Nov 2012 02:02:48 -0800 Date: Wed, 28 Nov 2012 02:02:48 -0800 (PST) From: AndyG To: dev@activemq.apache.org Message-ID: <1354096968855-4659873.post@n4.nabble.com> In-Reply-To: References: Subject: Re: InactivityMonitor - Creating too frequent threads MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I agree. I am using ActiveMQ within OpenEJB and under our normal load I have about 140 threads alive. Just about the only thread deaths I have are the 'ActiveMQ InactivityMonitor Worker' and 'ActiveMQ BrokerService[name] Task-[count]. I tend to wait for a stable snapshot and then change the pool value to 2 minutes in the AbstractInactivityMonitor.java (default 10 seconds) and TaskRunnerFactory.java (default 30 seconds) and so far I have not seen the thread count creep up due to the fact that the pools are unbounded. It would make life easier if these values were a configuration option or at least taken from a System property. Maybe a JIRA is in order? Andy. -- View this message in context: http://activemq.2283324.n4.nabble.com/InactivityMonitor-Creating-too-frequent-threads-tp4656752p4659873.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.