Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 86459 invoked from network); 20 Feb 2008 08:12:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Feb 2008 08:12:20 -0000 Received: (qmail 42368 invoked by uid 500); 20 Feb 2008 08:12:14 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 42345 invoked by uid 500); 20 Feb 2008 08:12:14 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 42336 invoked by uid 99); 20 Feb 2008 08:12:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2008 00:12:14 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2008 08:11:36 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B9915234C03E for ; Wed, 20 Feb 2008 00:11:43 -0800 (PST) Message-ID: <144540182.1203495103758.JavaMail.jira@brutus> Date: Wed, 20 Feb 2008 00:11:43 -0800 (PST) From: "Serge Tsv (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-3378) Derby's timer thread should have a name that identifies it as belong to a derby instance In-Reply-To: <22456904.1201894867875.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570600#action_12570600 ] Serge Tsv commented on DERBY-3378: ---------------------------------- I do also think that maintaining some thread-naming policy could be quite helpful for debugging purposes, especially when running embedded in an environment with many threads (including Timer ones) started by other frameworks. I think that having an existing prefix "derby." added to a thread name might be sufficient. But somehow a thread name generation should be centralized I guess, so that a thread naming policy could be changed without affecting the rest of the code. Should a new issue be created for this? Thanks! > Derby's timer thread should have a name that identifies it as belong to a derby instance > ---------------------------------------------------------------------------------------- > > Key: DERBY-3378 > URL: https://issues.apache.org/jira/browse/DERBY-3378 > Project: Derby > Issue Type: Improvement > Components: Newcomer, Services > Reporter: Daniel John Debrunner > Priority: Minor > > Looking at the threads with jconsole when derby is running shows derby's timer thread as Timer-0. > All other derby threads are given a name starting with 'derby.', would be useful if the same was true for the timer thread. > In SingletonTimerFactory just use the Timer constructor that takes a name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.