Route Tomcat archive through MASS

[bric3]

What Does This Do

When MASS_READ_URL is present, the Spring Boot Tomcat nested application resolves the Tomcat ZIP through MASS at /internal/artifact/dlcdn.apache.org. Without that environment variable, local builds keep using https://dlcdn.apache.org.

Motivation

CI should send build-time archive downloads through MASS when the upstream host is already allowed. The Tomcat archive host is covered by the existing .apache.org:443 suffix entry.

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 linking keywords when referencing an issue.
• Update CODEOWNERS on source file addition, migration, or deletion. Not applicable.
• Update public documentation with any new configuration flags or behaviors. Not applicable.

Jira ticket: APMLP-1406, APMLP-1402

[AlexeyKuznetsov-DD]

LGTM. Left minor question.

[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.00 s	14.09 s	[-2.0%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.92 s	13.06 s	[-2.2%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	16.57 s	16.30 s	[+0.5%; +2.8%] (maybe worse)
startup:petclinic:iast:Agent	16.63 s	16.58 s	[-0.7%; +1.3%] (no difference)
startup:petclinic:profiling:Agent	16.36 s	16.68 s	[-3.3%; -0.5%] (maybe better)
startup:petclinic:tracing:Agent	15.92 s	15.80 s	[-0.4%; +2.0%] (no difference)

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

[bric3]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-04 17:10:34 UTC ℹ️ Start processing command /merge

---

2026-06-04 17:10:40 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-06-04 19:01:39 UTC ℹ️ MergeQueue: This merge request was merged