[ 
https://issues.apache.org/jira/browse/HADOOP-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738879#comment-16738879
 ] 

Wei-Chiu Chuang edited comment on HADOOP-16016 at 1/10/19 6:16 AM:
-------------------------------------------------------------------

+1 [~ajisakaa] thanks for figuring it out!
I'm wondering if we should document it or attach a release note somewhere, 
since the error message is not obvious, and a user who upgrades JDK would 
suddenly not able to start DataNode because of this issue.


was (Author: jojochuang):
+1 [~ajisakaa] thanks for figuring it out!
I'm wondering if we should document it or attach a release note somewhere, 
since the error message is not obvious, and a user who upgrades JDK would 
suddenly be able to start DataNode because of this issue.

> TestSSLFactory#testServerWeakCiphers sporadically fails in precommit builds
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-16016
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16016
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, test
>         Environment: Java 1.8.0_191 or upper
>            Reporter: Jason Lowe
>            Assignee: Akira Ajisaka
>            Priority: Major
>         Attachments: HADOOP-16016-002.patch, HADOOP-16016.01.patch, 
> HADOOP-16016.03.patch
>
>
> I have seen a couple of precommit builds across JIRAs fail in 
> TestSSLFactory#testServerWeakCiphers with the error:
> {noformat}
> [ERROR]   TestSSLFactory.testServerWeakCiphers:240 Expected to find 'no 
> cipher suites in common' but got unexpected 
> exception:javax.net.ssl.SSLHandshakeException: No appropriate protocol 
> (protocol is disabled or cipher suites are inappropriate)
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to