db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Tsv (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3378) Derby's timer thread should have a name that identifies it as belong to a derby instance
Date Wed, 20 Feb 2008 08:11:43 GMT

    [ 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.


Mime
View raw message