[jboss-jira] [JBoss JIRA] Updated: (JBAS-6966) Some tests fail with IBM JDK - java.lang.IllegalArgumentException: SSLv2Hello

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.