What Does This Do

Prevent long-lived JDK infrastructure threads from inheriting the request that happens to create them:

• Start virtual I/O pollers under root context, restoring the caller’s context afterward.
• Exclude the JDK HTTP client’s internal selector task from virtual-thread context capture.
• Preserve propagation for ordinary application virtual threads.

Motivation

irst-use initialization under an active request could capture that request in permanent SubPoller threads. JDK 26’s virtual HTTP selector could also retain its creating request for the client’s lifetime.

These threads do not belong to the request, and their continuations cannot be released until they terminate. The smoke-test continuation diagnostic exposed both paths.

Simply disabling async capture is insufficient: virtual-thread instrumentation also saves the raw context independently.

flowchart TD
    A[Active request] --> B[Create HTTP client]
    B --> C[Virtual selector]
    C --> D[Initialize shared I/O pollers]
    D --> E[Permanent virtual pollers]

    C -. Before: retains request .-> F[Request context and continuation]
    E -. Before: retains request .-> F

    C --> G[After: no inherited request]
    D --> H[After: initialize under root context]

    style F fill:#ffdddd,stroke:#cc3333
    style G fill:#ddffdd,stroke:#339933
    style H fill:#ddffdd,stroke:#339933

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]