JDK-8277090 : jsr166 refresh for jdk19
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.concurrent
  • Affected Version: 11.0.10-oracle
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2021-11-13
  • Updated: 2024-04-10
  • Resolved: 2022-05-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 19
19 b21Fixed
Related Reports
CSR :  
JDK-8285450 - jsr166 refresh for jdk19
Duplicate :  
JDK-8257781 - Add ForkJoinTask.adaptInterruptible
Relates :  
JDK-8295962 - Reference to State in Task.java is ambiguous when building with JDK 19
Relates :  
JDK-8330017 - ForkJoinPool stops executing tasks due to ctl field Release Count (RC) overflow
Relates :  
JDK-8317960 - [17u] Excessive CPU usage on AbstractQueuedSynchronized.isEnqueued
Relates :  
JDK-8327501 - Common ForkJoinPool prevents class unloading in some cases
Relates :  
JDK-8301216 - ForkJoinPool invokeAll() ignores timeout
Description
[Renamed from "ForkJoinPool initialization interferes with other static initialization", because the related changes can't be disentangled.]

This CR mainly provides updates enabling planned loom and related jdk enhancements. The main goal is to streamline initialization by removing other JDK  dependencies including VarHandles, and access control (currently only when deprecated SecurityManagers are not used; eventually further removable). It also includes performance improvements for async usages, as well as a few new methods (ForkJoinPool.lazySubmit and setParallelism) needed by other jdk enhancements. Also, to simplify upcoming integrations, it includes java.util.concurrent API updates in Future and ExecutorService that are introduced by loom, but do not directly involve VirtualThreads, and are independently useful.
Comments
Changeset: 00e6c63c Author: Doug Lea <dl@openjdk.org> Date: 2022-05-04 19:24:19 +0000 URL: https://git.openjdk.java.net/jdk/commit/00e6c63cd12e3f92d0c1d007aab4f74915616ffb
04-05-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/8536 Date: 2022-05-04 12:30:53 +0000
04-05-2022
A pull request was submitted for review. URL: https://git.openjdk.java.net/jdk/pull/8490 Date: 2022-05-01 10:53:55 +0000
01-05-2022
Note: I edited description to combine initialization improvements with other mainly-loom-related updates because they should be considered at the same time.
22-04-2022
My view is that is a performance bug with impact that has gotten increasingly worse over past few releases and even more so for loom.
15-11-2021
[~dl] This seems like an enhancement request, not a bug. Is this for mainline or for Loom?
15-11-2021
On further thought and experimentation, steps (2) and (4) are less likely to be useful, and they both require adding public methods, so should just be noted as potential further steps for now. Anyone interested in looking at the other changes (ForkJoin{Pool,Task}, CountedCompleter) can find them in jsr166 cvs (via http://gee.cs.oswego.edu/dl/concurrency-interest/index.html)
14-11-2021