Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 10022 invoked from network); 27 Jul 2010 14:39:05 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 27 Jul 2010 14:39:05 -0000 Received: (qmail 37543 invoked by uid 500); 27 Jul 2010 14:39:05 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 37441 invoked by uid 500); 27 Jul 2010 14:39:04 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 37433 invoked by uid 99); 27 Jul 2010 14:39:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jul 2010 14:39:04 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL 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; Tue, 27 Jul 2010 14:38:58 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1OdlIk-0007WO-3d for users@activemq.apache.org; Tue, 27 Jul 2010 07:38:38 -0700 Message-ID: <29277094.post@talk.nabble.com> Date: Tue, 27 Jul 2010 07:38:38 -0700 (PDT) From: nervousbadger To: users@activemq.apache.org Subject: ActiveMQ Session Task thread name MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2458_14872830.1280241518109" X-Nabble-From: nervousbadger@googlemail.com ------=_Part_2458_14872830.1280241518109 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi there, We are using ActiveMQ v5.3.1. We have multiple sessions per connection, each processing incoming messages. The problem we have is that each session dispatch thread has the same name - "ActiveMQ Session Task". We would like each thread to have a unique name to aid debugging using our application log files. Looking at the code for ActiveMQConnection, I can see: public TaskRunnerFactory getSessionTaskRunner() { synchronized (this) { if (sessionTaskRunner == null) { sessionTaskRunner = new TaskRunnerFactory("ActiveMQ Session Task", ThreadPriorities.INBOUND_CLIENT_SESSION, false, 1000, isUseDedicatedTaskRunner()); } } return sessionTaskRunner; } So it looks like I can't configure this. Is there a way to do this, or will I need to patch the code? Thanks, Pete. -- View this message in context: http://old.nabble.com/ActiveMQ-Session-Task-thread-name-tp29277094p29277094.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. ------=_Part_2458_14872830.1280241518109--