Skip to content
Bluetape4k docs1.11

Virtual Threads for JDK 21

Latest stable Based on Bluetape4k release 1.11.0

Java 21 virtual-thread implementation module. This manual connects that purpose to the current build, source entry points, tests, configuration resources, and lifecycle evidence instead of duplicating the README feature list.

Use bluetape4k-virtualthread-jdk21 when the application needs scope ownership, cancellation, executor lifecycle, blocking boundaries, and shutdown. Start with the source entry points below and confirm that their ownership and failure contracts match the calling component. Prefer a smaller standard-library or already-adopted module when it satisfies the same contract without another runtime boundary.

dependencies {
implementation(platform("io.github.bluetape4k:bluetape4k-dependencies:<version>"))
implementation("io.github.bluetape4k:bluetape4k-virtualthread-jdk21")
}

Gradle project path: :bluetape4k-virtualthread-jdk21. Source directory: virtualthread/jdk21.

The first source-level concepts to inspect are Jdk21VirtualThreadRuntime, and Jdk21StructuredTaskScopeProvider. File names are navigation anchors; read each declaration and its tests before treating it as a public contract.

Add the coordinate above, refresh Gradle, and start from the smallest entry point that owns the required task. Open Jdk21VirtualThreadRuntime first; it is a concrete source entry point for the module.

Entry pointWhat to verify
Jdk21VirtualThreadRuntimeInspect this declaration’s constructors, functions, and ownership contract.
Jdk21StructuredTaskScopeProviderInspect this declaration’s constructors, functions, and ownership contract.

The README evidence is organized around Overview, UML, Main Implementations, Jdk21VirtualThreadRuntime, Jdk21StructuredTaskScopeProvider, ServiceLoader Configuration, Build Configuration, Dependencies, Gradle Dependencies, and Gradle Usage Example. Use those topics as a navigation map, then confirm behavior in source and tests. Keep adoption narrow and connect owned resources to the caller lifecycle.

The current build declares these integration edges:

api(project(":bluetape4k-virtualthread-api"))
implementation(project(":bluetape4k-logging"))
implementation(libs.kotlinx.coroutines.core)

Treat compileOnly edges as caller-provided capabilities and verify runtime availability before using their APIs.

Configuration resources found in the module:

Read property names and defaults from these resources and the binding source before overriding them.

Failure semantics are defined by the linked entry points and tests, not inferred from the artifact name. Keep cancellation and timeout signals intact, close owned resources, and translate backend exceptions only at a boundary that can add a stable domain contract. Use the test anchors below to verify the exact behavior before adding retries or fallbacks.

Track active work, queue depth, cancellation, timeout, executor saturation, and shutdown completion. Keep capacity, timeout, retry, and shutdown settings next to the component that owns the resource; avoid process-wide defaults that hide which caller accepted the trade-off.

Run the module test task:

Terminal window
./gradlew :bluetape4k-virtualthread-jdk21:test --no-configuration-cache

Representative test anchors:

No dedicated workshop path is registered in the manual manifest. Use the module README and the representative tests above as runnable evidence.

This page documents the repository state represented by the linked source and tests. It does not turn optional backends into application defaults or claim performance without a benchmark artifact. Re-check compatibility and lifecycle notes when the module version changes.

These diagrams are loaded directly from README assets published with the 1.11.0 release and pinned to its immutable commit. They describe this manual’s released structure and runtime flows, not later Snapshot changes. Select a preview to open the SVG at the same release commit.

JDK 21 virtual-thread runtime and StructuredTaskScope provider structure

Section titled “JDK 21 virtual-thread runtime and StructuredTaskScope provider structure”

JDK 21 virtual-thread runtime and StructuredTaskScope provider structure

Release README: virtualthread/jdk21/README.md