Varada M

Results 18 comments of Varada M

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

Thanks @GoeLin for pointing that out. I tested with wrong jtreg version. I will fix the errors.

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

Hi @GoeLin, can you please review the changes. Test is passing now with jtreg 6.1

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

@jaikiran @GoeLin Could you please review the code? Thank you, Varada

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

Thank you @jaikiran for reviewing the changes.

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

/approval request org.junit.jupiter.api is not supported. Therefore, I have added the similar annotations supported by org.junit.*

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

/approval JDK-8305906 request org.junit.jupiter.api is not supported. Therefore, I have added the similar annotations supported by org.junit.*

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

> Hi @varada1110 please explain how you addressed the issues that came up in the 17u backport. Also explain how you tested to show the same issues don't surface in...

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

Hi @GoeLin , Could you please review the code? All checks have passed and test is passing with updated jtreg

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

/approval JDK-8305906 request test is passing with updated jtreg and PR is clean.

8305906: HttpClient may use incorrect key when finding pooled HTTP/2 connection for IPv6 address

/integrate