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 "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2020/11/29 18:50:00 UTC
[jira] [Commented] (DERBY-7094) Replace Derby thread management
with machinery from java.util.concurrent
[ https://issues.apache.org/jira/browse/DERBY-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240328#comment-17240328 ]
Richard N. Hillegas commented on DERBY-7094:
--------------------------------------------
Linking to DERBY-7088 because this issue surfaced during the testing of Open JDK build 16-ea+26-1764.
> Replace Derby thread management with machinery from java.util.concurrent
> ------------------------------------------------------------------------
>
> Key: DERBY-7094
> URL: https://issues.apache.org/jira/browse/DERBY-7094
> Project: Derby
> Issue Type: Task
> Components: Services
> Affects Versions: 10.16.0.0
> Reporter: Richard N. Hillegas
> Priority: Major
>
> Derby thread management should be re-written to use the threading machinery in java.util.concurrent, rather than java.lang.ThreadGroup. This issue arises because ThreadGroup.isDestroyed() and ThreadGroup.destroy() were deprecated by Open JDK build 16-ea+26-1764. They will be removed from some future rev of the JDK. Their deprecation and planned removal are discussed on the following pages (thanks to Dalibor Topic for these references):
> * https://github.com/openjdk/jdk/pull/1318
> * https://bugs.openjdk.java.net/browse/JDK-8256644
> * https://openjdk.java.net/jeps/8252885
--
This message was sent by Atlassian Jira
(v8.3.4#803005)