[jboss-jira] [JBoss JIRA] Commented: (JBAS-6966) Some tests fail with IBM JDK - java.lang.IllegalArgumentException: SSLv2Hello
[
https://jira.jboss.org/jira/browse/JBAS-6966?page=com.atlassian.jira.plug...
]
Shelly McGowan commented on JBAS-6966:
--------------------------------------
IBM JDK 5 nor 6 supports specifying SSLv2Hello:
http://www.ibm.com/developerworks/java/jdk/security/60/secguides/jsse2Doc...
http://www.ibm.com/developerworks/java/jdk/security/50/secguides/jsse2Doc...
Specifically,
IBM implementation supports the following protocols: SSL, SSLv3, TLS, TLSv1, and SSL_TLS
for engine class SSLContext or the API setEnabledProtocols in the SSLSocket or
SSLServerSocket classes. It does not support specifying SSLv2Hello. A server side
connection always accepts an SSLv2Hello. The IBM SSLContext getInstance factory method can
be used to control which protocols actually get enabled for an SSL connection. Using the
SSLContext getInstance or the setEnabledProtocols method give the same result. The Sun
JSSE controls which protocols are actually enabled for an SSL connection through
setEnabledProtocols.
Some tests fail with IBM JDK - java.lang.IllegalArgumentException:
SSLv2Hello
-----------------------------------------------------------------------------
Key: JBAS-6966
URL: https://jira.jboss.org/jira/browse/JBAS-6966
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.1.0.CR1
Environment: IBM JDK 1.5
Reporter: Martin Malina
Assignee: Shelly McGowan
Attachments: SSLv2Hello-error
Some tests in the testsuite are failing due to IBM JDK not supporting the SSLv2Hello
protocol:
15:10:46,727 ERROR [AbstractKernelController] Error installing to Start:
name=jboss:service=invoker,socketType=SSLSocketFactory,type=jrmp,wantsClientAuth=true
state=Create mode=Manual requiredState=Installed
java.lang.IllegalArgumentException: SSLv2Hello
at com.ibm.jsse2.mb.a(mb.java:24)
at com.ibm.jsse2.lb.<init>(lb.java:41)
at com.ibm.jsse2.hc.setEnabledProtocols(hc.java:57)
at
org.jboss.security.ssl.DomainServerSocketFactory.createServerSocket(DomainServerSocketFactory.java:267)
at
org.jboss.security.ssl.DomainServerSocketFactory.createServerSocket(DomainServerSocketFactory.java:226)
at
org.jboss.security.ssl.RMISSLServerSocketFactory.createServerSocket(RMISSLServerSocketFactory.java:120)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:638)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:272)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:219)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:398)
...
This problem was previously reported as JBPAPP-626 but never fixed. I'm creating a
new JIRA since it now affects more testcases.
These testcases fail:
org.jboss.test.jrmp.test.CustomSocketsUnitTestCase
org.jboss.test.jrmp.test.SSLFailuresSocketsUnitTestCase
org.jboss.test.jrmp.test.SSLSocketsUnitTestCase
org.jboss.test.pooled.test.SSLSocketsUnitTestCase
We can still leave it as it is - meaning documenting these failures as known issues with
IBM JDK. I just wanted to make sure we know about it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira