[
https://issues.apache.org/jira/browse/DERBY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570604#action_12570604
]
Kristian Waagan commented on DERBY-3378:
----------------------------------------
Hi Serge,
You are of course welcome to start working on this issue, and other issues you
might find interesting!
You need developer access in JIRA to assign yourself to this issue. Please send
a mail requesting developer access to derby-dev@db.apache.org (include your
JIRA user name).
>From what I read above, I think it will be a good move to fix what is
>originally described in the issue first.
You can find some pieces of advice for Derby development on the wiki:
http://wiki.apache.org/db-derby/DerbyDev
Feel free to ask questions on the developer mailing list. Welcome to the Derby
community :)
> 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.
