JEP 543 Finalizes Structured Concurrency in JDK 28 After Seven Preview Rounds

Structured Concurrency Finalized

JEP 543, Structured Concurrency, has been integrated into JDK 28, transitioning the StructuredTaskScope API within java.util.concurrent to a final status. This finalization occurred without any API changes from its seventh preview in JDK 27, meaning codebases on JDK 27 can migrate by recompiling without the --enable-preview flag.

Longest Project Loom Preview Cycle

The finalization of JEP 543 marks the conclusion of the longest preview cycle for any Project Loom feature. Structured concurrency was first introduced as an incubator API in JDK 19 (JEP 428) and JDK 20 (JEP 437), then progressed through seven preview iterations across subsequent JDK releases up to JDK 27.

Core Objective and Problem Solved

The core objective of Structured Concurrency is to treat groups of related subtasks running in different threads as a single unit of work. This ensures that a failure in one subtask leads to the cancellation of others, and the parent scope cannot exit until all child threads have terminated. This addresses limitations in traditional ExecutorService and Future pipelines, where parent methods could return while subtasks continued, and failures only surfaced upon explicit Future.get() calls.

API Details

The API centers on the sealed interface StructuredTaskScope<T, R, R_X extends Throwable>, which is opened via static factory methods like open(). The join() method waits for subtasks, cancels others on the first failure, and throws ExecutionException. Each fork() call starts a virtual thread by default, and the close() method in a try-with-resources block cancels unfinished subtasks and waits for their threads to terminate.

Completion policies are defined through the Joiner<T, R, R_X> interface, offering methods such as Joiner.awaitAllSuccessfulOrThrow(), Joiner.allSuccessfulOrThrow(), Joiner.anySuccessfulOrThrow(), and Joiner.allUntil(Predicate) to manage subtask completion and cancellation behavior.