db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-3378) Derby's timer thread should have a name that identifies it as belong to a derby instance
Date Thu, 07 May 2009 13:42:30 GMT

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

Kathey Marsden reassigned DERBY-3378:
-------------------------------------

    Assignee:     (was: Serge Tsv)

Unassigning due to inactivity. Serge, please reassign yourself if you would like to continue
work on this issue.


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


Mime
View raw message