Fix Axis2 resumed message scope close order

[amarziali]

What Does This Do

Axis2 message resumption activates the child scope before the try-with-resources block closes its resumed parent, causing an out-of-order scope close.

Create the child span under the resumed parent, then activate it after the parent scope closes. This preserves trace parentage and correct scope ordering.

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-30T11:50:08.032526Z	d205b73	PR opened
🔒 Security Review	✅ Completed 2026-09-30T11:54:41.558428Z	d205b73	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.

[datadog-prod-us1-4]

More details

The child span remains created under the resumed parent but is activated only after that parent scope closes, preserving trace parentage while correcting scope order.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit d205b73 · @DataDog review to ask questions}

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.24% (+0.00%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: d205b73 | 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	13.99 s	13.96 s	[-0.4%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.92 s	13.09 s	[-2.1%; -0.5%] (maybe better)
startup:petclinic:appsec:Agent	17.09 s	17.08 s	[-0.7%; +0.9%] (no difference)
startup:petclinic:iast:Agent	17.01 s	17.12 s	[-1.7%; +0.4%] (no difference)
startup:petclinic:profiling:Agent	16.82 s	16.75 s	[-0.7%; +1.6%] (no difference)
startup:petclinic:sca:Agent	17.08 s	16.86 s	[+0.3%; +2.2%] (maybe worse)
startup:petclinic:tracing:Agent	16.24 s	16.30 s	[-1.3%; +0.6%] (no difference)

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