From dev-return-15365-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Wed May 20 09:35:41 2009 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 21868 invoked from network); 20 May 2009 09:35:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 May 2009 09:35:41 -0000 Received: (qmail 12347 invoked by uid 500); 20 May 2009 09:28:32 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 12290 invoked by uid 500); 20 May 2009 09:28:32 -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 12111 invoked by uid 99); 20 May 2009 09:28:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2009 09:28:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 May 2009 09:28:22 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M6i5h-0004ZS-SU for dev@activemq.apache.org; Wed, 20 May 2009 02:28:01 -0700 Message-ID: <23631976.post@talk.nabble.com> Date: Wed, 20 May 2009 02:28:01 -0700 (PDT) From: Aleksi Kallio To: dev@activemq.apache.org Subject: Why UseDedicatedTaskRunner is true by default? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: aleksi.kallio@csc.fi X-Virus-Checked: Checked by ClamAV on apache.org Hello, We have had problems with too many threads killing the broker. They were solved by setting UseDedicatedTaskRunner to false. The reason was that we are using a lot of temporary topics. TemporaryTopic is a Destination, and broker creates a TaskRunner thread for each of them. To me this seems quite counterintuitive, because TemporaryTopic (obtained from Message.getJMSReplyTo) is something that you can use and throw away without much thought. It is surprising that by default they block a thread on the broker, i.e., reserve quite a heavy resource. Because of the excessive thread creation, using dedicated TaskRunners was also slower. If they are preferred, shouldn't temporary topics (and queues) be handled in a more lighweight manner? Cheers, Aleksi -- View this message in context: http://www.nabble.com/Why-UseDedicatedTaskRunner-is-true-by-default--tp23631976p23631976.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.