On Thu, 11 Feb 2021 12:08:54 GMT, Fernando Guallini <[email protected]>
wrote:
>> The server side is binding to the wildcard address which has been a source
>> of instability in many networking tests due to javax.net.ssl.SSLException:
>> Connection reset. Changing the following tests to bind to loopback address
>> fixes intermittent failures:
>> sun/security/ssl/SSLSocketImpl/ReverseNameLookup.java
>> javax/net/ssl/TLSCommon/TLSTest.java
>> sun/security/ssl/CipherSuite/SupportedGroups.java
>>
>>
>> javax/net/ssl/SSLSession/TestEnabledProtocols.java still throws a connection
>> reset occasionally because the server closes the connection before the
>> client is done during handshake. That race condition cannot be completely
>> removed in this test, thus is now handled and logged.
>
> Fernando Guallini has updated the pull request incrementally with one
> additional commit since the last revision:
>
> check exception type
test/jdk/javax/net/ssl/SSLSession/TestEnabledProtocols.java line 155:
> 153: && "Connection reset".equals(cause.getMessage())) {
> 154: System.out.println("Client SSLException:");
> 155: ssle.printStackTrace(System.out);
Sorry for nit picking - but I would keep that tracing in the catch clause
above.
} catch (SSLException ssle) {
if (isConnectionReset(ssle)) {
System.out.println("Client SSLException:");
ssle.printStackTrace(System.out);
} else {
failTest(ssle, "Client got UNEXPECTED SSLException:");
}
}
```
-------------
PR: https://git.openjdk.java.net/jdk/pull/2405