Preserve Jetty 12 request task invocation types

[amarziali]

What Does This Do

JettyRunnableWrapper hides the wrapped task’s Invocable contract, causing Jetty to classify every wrapped task as blocking. For nonblocking HTTP/2 handlers, this can introduce unnecessary executor dispatch or producer handoffs.

Implement Invocable on the wrapper and delegate getInvocationType() to the original task, preserving Jetty’s scheduling decisions and existing context propagation.

Motivation

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]

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-21T12:50:41.738394Z	c377bc4	PR opened
🔒 Security Review	✅ Completed 2026-09-21T12:52:16.231179Z	c377bc4	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[amarziali]

@DataDog review

[datadog-datadog-prod-us1-2]

More details

The wrapper keeps each Jetty invocation type. Plain Runnable tasks keep the blocking default, and context handling stays unchanged.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit c377bc4 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.02 s	14.02 s	[-0.7%; +0.6%] (no difference)
startup:insecure-bank:tracing:Agent	12.98 s	13.04 s	[-1.3%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	17.59 s	17.32 s	[+0.7%; +2.5%] (maybe worse)
startup:petclinic:iast:Agent	17.46 s	17.69 s	[-2.1%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	17.41 s	17.47 s	[-1.5%; +0.8%] (no difference)
startup:petclinic:sca:Agent	17.63 s	17.59 s	[-0.7%; +1.1%] (no difference)
startup:petclinic:tracing:Agent	16.80 s	16.76 s	[-0.9%; +1.3%] (no difference)

Commit: c377bc4f · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[datadog-datadog-prod-us1-2]

More details

The wrapper delegates Jetty invocation types and keeps plain Runnable tasks blocking. Context propagation stays unchanged.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit c377bc4 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[amarziali]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-22 11:49:20 UTC ℹ️ Start processing command /merge

---

2026-09-22 11:49:24 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-09-22 13:15:57 UTC ℹ️ MergeQueue: This merge request was merged