On Fri, 5 Feb 2021 17:45:45 GMT, Rajan Halade <rhal...@openjdk.org> wrote:
>> test/jdk/javax/net/ssl/SSLSession/TestEnabledProtocols.java line 145: >> >>> 143: // The server side may have closed the socket. >>> 144: System.out.println("Client SSLException:"); >>> 145: ssle.printStackTrace(System.out); >> >> If security / TLS experts agree that this is OK, then it is OK for me. Not >> being an expert, I'd be concerned that catching plain SSLException might be >> too wide and that this might hide errors. In that case, and if the error is >> intermittent, one possibility could be to respin the test in case of >> SSLException (do client side and server side again) and fail if the second >> attempts fails too. > > You can use getCause() to examine reason for SSLException. Sure. Narrowed down SSLException handling by using getCause() in last commit. ------------- PR: https://git.openjdk.java.net/jdk/pull/2405