Virtual Threads for JDK 25
Latest stable Based on Bluetape4k release 1.11.0
Problem
Section titled “Problem”Java 25 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.
When to use
Section titled “When to use”Use bluetape4k-virtualthread-jdk25 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.
Coordinates
Section titled “Coordinates”dependencies { implementation(platform("io.github.bluetape4k:bluetape4k-dependencies:<version>")) implementation("io.github.bluetape4k:bluetape4k-virtualthread-jdk25")}Gradle project path: :bluetape4k-virtualthread-jdk25. Source directory: virtualthread/jdk25.
Concepts
Section titled “Concepts”The first source-level concepts to inspect are Jdk25VirtualThreadRuntime, and Jdk25StructuredTaskScopeProvider. File names are navigation anchors; read each declaration and its tests before treating it as a public contract.
Quick start
Section titled “Quick start”Add the coordinate above, refresh Gradle, and start from the smallest entry point that owns the required task. Open Jdk25VirtualThreadRuntime first; it is a concrete source entry point for the module.
API by task
Section titled “API by task”| Entry point | What to verify |
|---|---|
Jdk25VirtualThreadRuntime | Inspect this declaration’s constructors, functions, and ownership contract. |
Jdk25StructuredTaskScopeProvider | Inspect this declaration’s constructors, functions, and ownership contract. |
Patterns
Section titled “Patterns”The README evidence is organized around Overview, Implementation Structure, Main Implementations, Jdk25VirtualThreadRuntime, Jdk25StructuredTaskScopeProvider, 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.
Integrations
Section titled “Integrations”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
Section titled “Configuration”Configuration resources found in the module:
io.bluetape4k.concurrent.virtualthread.StructuredTaskScopeProviderio.bluetape4k.concurrent.virtualthread.VirtualThreadRuntime
Read property names and defaults from these resources and the binding source before overriding them.
Failures
Section titled “Failures”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.
Operations
Section titled “Operations”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.
Testing
Section titled “Testing”Run the module test task:
./gradlew :bluetape4k-virtualthread-jdk25:test --no-configuration-cacheRepresentative test anchors:
Workshops
Section titled “Workshops”No dedicated workshop path is registered in the manual manifest. Use the module README and the representative tests above as runnable evidence.
Limitations
Section titled “Limitations”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.
Release diagrams
Section titled “Release diagrams”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 25 virtual-thread runtime and StructuredTaskScope Joiner provider structure
Section titled “JDK 25 virtual-thread runtime and StructuredTaskScope Joiner provider structure”Release README: virtualthread/jdk25/README.md
