Avoid queue-timing metadata reads before JFR is ready

[amarziali]

What Does This Do

ThreadPoolExecutor instrumentation collected queue metadata before the timer helper checked whether JFR was ready. Move that readiness check ahead of metadata collection, preserving trace propagation and delayed profiling startup.

Avoiding queue.size() also avoids unnecessary lock acquisition—and potential blocking under contention—for queues such as ArrayBlockingQueue and PriorityBlockingQueue.

Share the readiness predicate through QueueTimerHelper, retaining its native-image exclusion and defensive check for other callers.

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]

[datadog-datadog-prod-us1]

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 62.79% (+3.69%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4bae9f2 | Docs | Give us feedback!}

[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.80 s	14.77 s	[-0.6%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	13.67 s	13.76 s	[-1.6%; +0.4%] (no difference)
startup:petclinic:appsec:Agent	17.09 s	16.95 s	[-0.2%; +1.9%] (no difference)
startup:petclinic:iast:Agent	16.94 s	17.00 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.51 s	16.87 s	[-3.1%; -1.1%] (significantly better)
startup:petclinic:sca:Agent	16.87 s	16.85 s	[-0.8%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	16.09 s	15.59 s	[-1.1%; +7.5%] (no difference)

Commit: 4bae9f2b · 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.

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[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-17T16:24:43.250696Z	4bae9f2	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-17T16:24:48.240982Z	4bae9f2	Draft marked ready

ℹ️ 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.

[datadog-datadog-prod-us1]

More details

The readiness guard runs before queue type and size reads. The defensive helper guard stays in place for other callers.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[jbachorik]

Looks good

[bric3]

Nice tweak !

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-21 07:18:27 UTC ℹ️ Start processing command /merge

---

2026-09-21 07:18:32 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-21 08:31:23 UTC ❌ MergeQueue: The build pipeline failed for this merge request

Build pipeline has failing jobs for 9e18cc4:

• test_inst: [semeru8, 2/8]
• test_inst: [27, 6/8]
• test_inst: [21, 2/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-09-21 09:39:56 UTC ℹ️ Start processing command /merge

---

2026-09-21 09:40:00 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-09-21 10:52:15 UTC ℹ️ MergeQueue: This merge request was merged