8297798: Timeout with DTLSOverDatagram test template

[GoeLin]

I backport this to streamline testing based on the change in 17.

I had to resolve DTLSOverDatagram because the code in 11 uses classes, where the code in 17 uses records.
The added code is identical in 11 and 17.

Tests pass.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8297798 needs maintainer approval

Issue

• JDK-8297798: Timeout with DTLSOverDatagram test template (Bug - P3 - Approved)

Reviewers

• Matthias Baesken (@MBaesken - Reviewer) ⚠️ Review applies to 10191f66

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/2629/head:pull/2629
$ git checkout pull/2629

Update a local copy of the PR:
$ git checkout pull/2629
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/2629/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2629

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/2629.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! 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]

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

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

8297798: Timeout with DTLSOverDatagram test template

Reviewed-by: mbaesken

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

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

[mlbridge]

Webrevs

• 02: Full (71bc0af8)
• 01: Full - Incremental (10191f66)
• 00: Full (10191f66)

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout goetz_backport_8297798
git fetch https://git.openjdk.org/jdk11u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@GoeLin this pull request can not be integrated into master due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout goetz_backport_8297798
git fetch https://git.openjdk.org/jdk11u-dev.git master
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge master"
git push

[GoeLin]

/integrate

[openjdk]

Going to push as commit 0073602.

[openjdk]

@GoeLin Pushed as commit 0073602.

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