Skip to content

fix: add default JDK dns resolver#4496

Merged
pablocarle merged 6 commits into
v3.x.xfrom
reboot/fix/resolver-dns
Mar 4, 2026
Merged

fix: add default JDK dns resolver#4496
pablocarle merged 6 commits into
v3.x.xfrom
reboot/fix/resolver-dns

Conversation

@pablocarle
Copy link
Copy Markdown
Contributor

Description

Force the use of the default JDK DNS resolver in webclient config

Linked to #3877

Type of change

  • fix: Bug fix (non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines of this project
  • PR title conforms to commit message guideline ## Commit Message Structure Guideline
  • I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • The java tests in the area I was working on leverage @nested annotations
  • Any dependent changes have been merged and published in downstream modules

Signed-off-by: Pablo Carle <pablo.carle@broadcom.com>
@EvaJavornicka EvaJavornicka moved this from New to In Progress in API Mediation Layer Backlog Management Mar 4, 2026
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Mar 4, 2026

@pablocarle pablocarle merged commit 4d87cc3 into v3.x.x Mar 4, 2026
81 of 84 checks passed
@pablocarle pablocarle deleted the reboot/fix/resolver-dns branch March 4, 2026 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Sensitive Sensitive change that requires peer review size/S

Projects

Development

Successfully merging this pull request may close these issues.

3 participants