What Does This Do

Disable async context capture only while TimeoutAccessImpl.clear() registers its timeout-cancellation callback, using the existing async-propagation-disable instrumentation.

Add an exact class-filter exception for TimeoutAccessImpl. The existing TimeoutAccessImpl$* entry covers nested classes, not the enclosing class containing clear().

Motivation

Play 2.6–2.8 smoke diagnostics exposed unresolved continuations captured by this cleanup callback. It waits on request-entity completion, which can remain unresolved even after the response completes.

This callback only cancels a timer; it does not need request context. Actual timeout handlers and normal request propagation remain unchanged.

flowchart LR
    A[Response completes] --> B[TimeoutAccessImpl.clear]
    B --> C[Register cancellation callback]
    C --> D[Wait for entity completion]
    D --> E[Cancel timeout task]
    B -. Previously captured request context .-> F[Unresolved continuation]
    style F fill:#f8d7da,stroke:#dc3545
    style C fill:#d4edda,stroke:#28a745

Here we remove the unwanted context capture without changing cancellation behavior.

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]