You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Serge Tsv (JIRA)" <ji...@apache.org> on 2008/02/21 08:50:43 UTC

[jira] Assigned: (DERBY-3378) Derby's timer thread should have a name that identifies it as belong to a derby instance

     [ https://issues.apache.org/jira/browse/DERBY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Tsv reassigned DERBY-3378:
--------------------------------

    Assignee: Serge Tsv

> 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
>            Assignee: Serge Tsv
>            Priority: Minor
>         Attachments: DERBY-3378.diff
>
>
> 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.