db-derby-dev mailing list archives

[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 17:39:43 GMT

[ https://issues.apache.org/jira/browse/DERBY-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570771#action_12570771
]
Daniel John Debrunner commented on DERBY-3378:
----------------------------------------------
I applied the patch but it fails to compile for me. Turns out the Timer constructors that
take a name were only added in JDK 1.5 and so do not compile with JDK 1.4 and J2ME/CDC/Foundation
which Derby still supports.
A specific implementation of the TimerFactory could be added for JDK 1.5 (that used new Timer("derby.timer",
...)) but I'm not sure it's worth it.
Sorry, I didn't realize that the constructor was new to JDK 1.5.
> 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.