8272996: JNDI DNS provider fails to resolve SRV entries when IPV6 stack is enabled

[macarte]

Backport of 4c169495a2c4bfdcbc82e94e9ca1ee0cc050daf9

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8272996: JNDI DNS provider fails to resolve SRV entries when IPV6 stack is enabled

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u-dev pull/176/head:pull/176
$ git checkout pull/176

Update a local copy of the PR:
$ git checkout pull/176
$ git pull https://git.openjdk.java.net/jdk17u-dev pull/176/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 176

View PR using the GUI difftool:
$ git pr show -t 176

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u-dev/pull/176.diff

[bridgekeeper]

👋 Welcome back macarte! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

@macarte This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8272996: JNDI DNS provider fails to resolve SRV entries when IPV6 stack is enabled

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 6650652: 8281460: Let ObjectMonitor have its own NMT category

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (23028de9)

[macarte]

/integrate

[openjdk]

@macarte
Your change (at version 23028de) is now ready to be sponsored by a Committer.

[AlekseiEfimov]

/sponsor

[openjdk]

Going to push as commit fc57ee6.
Since your change was applied there have been 2 commits pushed to the master branch:

• df5a29c: 8278185: Custom JRE cannot find non-ASCII named module inside
• 6650652: 8281460: Let ObjectMonitor have its own NMT category

Your commit was automatically rebased without conflicts.

[openjdk]

@AlekseiEfimov @macarte Pushed as commit fc57ee6.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.