[ygree]

What Does This Do

Reset two JMX caches when building native images so MBean servers created during the build are not retained in the executable. The tracer supplies the substitutions automatically, without application-side workaround code or additional dependencies.

Motivation

Quarkus applications using Oracle JDBC can create an MBean server during build-time initialization. The tracer’s JMX support makes that server reachable, causing GraalVM to reject the image heap and fail the build.

Additional Notes

• Added a minimal regression test without Oracle or Quarkus dependencies, using Quarkus’s initialization policy.
• Regression and runtime JMX checks pass with the fix on GraalVM 21 and 24.

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: APMS-20892

[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.81 s	14.78 s	[-0.8%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	13.60 s	13.65 s	[-1.1%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	17.80 s	17.45 s	[+1.1%; +2.9%] (significantly worse)
startup:petclinic:iast:Agent	17.40 s	17.51 s	[-1.6%; +0.3%] (no difference)
startup:petclinic:profiling:Agent	16.77 s	17.24 s	[-7.0%; +1.5%] (no difference)
startup:petclinic:sca:Agent	17.80 s	17.64 s	[+0.0%; +1.8%] (maybe worse)
startup:petclinic:tracing:Agent	16.65 s	16.77 s	[-1.6%; +0.2%] (no difference)

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