8323999: KeyAgreement cannot be initiated again after a failed initialization

[mpdonova]

This PR updates KeyAgreement to re-initialize the serviceIterator field when chooseProvider() is called and serviceIterator.hasNext() returns false. This can happen if KeyAgreement object has been initialized with an invalid key and then initialized with a valid key. (See accompanying test.)

---

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

Issue

• JDK-8323999: KeyAgreement cannot be initiated again after a failed initialization (Bug - P4)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28004/head:pull/28004
$ git checkout pull/28004

Update a local copy of the PR:
$ git checkout pull/28004
$ git pull https://git.openjdk.org/jdk.git pull/28004/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28004

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28004.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back mdonovan! 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 change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

@mpdonova The following label will be automatically applied to this pull request:

• security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (d6556fab)