JDK-8292045 : Release Note: ForkJoinPool and ThreadPoolExecutor do not use Thread::start to start worker threads
  • Type: Sub-task
  • Component: core-libs
  • Sub-Component: java.util.concurrent
  • Affected Version: 19
  • Priority: P4
  • Status: Resolved
  • Resolution: Delivered
  • Submitted: 2022-08-08
  • Updated: 2022-08-08
  • Resolved: 2022-08-08
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
19Resolved
Related Reports
Relates :  
Description
`java.util.concurrent.ForkJoinPool` and `java.util.concurrent.ThreadPoolExecutor` have changed in this release to not start worker threads with the `Thread.start` method. This may impact code that constructs a `ForkJoinPool` or `ThreadPoolExecutor` with a thread factory that creates worker `Thread`s that override the no-arg `start` method.  The overridden `start` method will not be invoked when worker threads are started. The change in behavior does not impact code that overrides the `ForkJoinWorkerThread.onStart()` method. The `onStart()` method will continue to be invoked by fork join worker threads when they start. A future release will re-examine the issue of thread factories creating threads that override the `start` method.