[
https://issues.apache.org/jira/browse/DERBY-7094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard N. Hillegas updated DERBY-7094:
---------------------------------------
Description:
MultiTest 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
was:
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
> Fix MultiTest to use thread management 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
>
> MultiTest 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)
