Fix JDBC URL parsing crash when no port specified

[ValentinZakharov]

What Does This Do

Guards the lastIndexOf(':') split in MODIFIED_URL_LIKE.doParse() so it only splits on a colon that appears after ://. If no such colon exists, the full URL is used as-is.

Motivation

DB2/AS400 JDBC URLs without an explicit port that contain = caused a crash in the agent:

java.lang.StringIndexOutOfBoundsException
    at java.lang.String.substring(String.java:1841)
    at datadog.trace.bootstrap.instrumentation.jdbc.JDBCConnectionUrlParser$2.doParse(JDBCConnectionUrlParser.java:109)
    at datadog.trace.bootstrap.instrumentation.jdbc.JDBCConnectionUrlParser$9.doParse(JDBCConnectionUrlParser.java:344)
    at datadog.trace.bootstrap.instrumentation.jdbc.JDBCConnectionUrlParser.parse(JDBCConnectionUrlParser.java:871)

The root cause: when a URL like jdbc:db2://host/db?user=foo is parsed, the code uses lastIndexOf(':') to find the parameter section separator. With no explicit port, the only : is the scheme colon (position 3), so urlPart1 is cut to just "db2". The subsequent urlPart1.substring(hostIndex + 3) - i.e. "db2".substring(6) - throws

URLs that trigger the bug:

• jdbc:db2://myhost/mydb?user=admin
• jdbc:db2://myhost/mydb?user=admin&connectionTimeout=30
• jdbc:as400://myhost/mydb?user=admin

URLs that work fine (explicit port puts a : past ://):

• jdbc:db2://myhost:50000/mydb:user=admin;password=secret;

Additional Notes

• The exception was swallowed by the parser's catch block, so the app didn't crash - but host and user were silently lost from the span.

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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f8a5e56949

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that 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.94 s	13.94 s	[-1.1%; +1.2%] (no difference)
startup:insecure-bank:tracing:Agent	12.86 s	12.92 s	[-1.6%; +0.7%] (no difference)
startup:petclinic:appsec:Agent	16.58 s	15.46 s	[-1.6%; +16.1%] (unstable)
startup:petclinic:iast:Agent	16.59 s	16.68 s	[-1.7%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.51 s	16.54 s	[-1.5%; +1.2%] (no difference)
startup:petclinic:tracing:Agent	15.83 s	15.89 s	[-1.5%; +0.7%] (no difference)

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

[amarziali]

thanks for fixing that. I left a couple of suggestions to encourage using TableTest in the the junit

[amarziali]

you can use @TableTest that we're actively using in the groovy to junit migration

[ValentinZakharov]

Thanks, fixed

[amarziali]

you can collapse the two test since the assertions look the same

[ValentinZakharov]

Good point! Thanks

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-04 12:51:17 UTC ℹ️ Start processing command /merge

---

2026-06-04 12:51:22 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

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