[jboss-jira] [JBoss JIRA] Updated: (JBAS-3570) SSLUnitTestCase testsuite failures when using the IBM JVM

[Matt Wringe (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3570?page=all ]

Matt Wringe updated JBAS-3570:
------------------------------

    Attachment: tomcat-ssl.log

The results I was getting was the same as the failures listed on the testsuite results page: http://testsuite.jboss.com/files/jboss-4.0.4.GA/Linux/2.6.9-34.ELsmp/IBM%20Corporation/1.4.2/html/org/jboss/test/web/test/ssl/SSLUnitTestCase.html

The connections are actually being refused due to the default algorithm being SunX506, whereas the IBM JDK uses the IbmX509 algorithm instead. The attached file shows the log when the tomcat-ssl server is started.

The algorithm can be changed by specifing it in the server.xml of the jbossweb-tomcat55.sar, but the tests then fail with another error.

I will bring up these issues in the forum before I comment on this issue any further.

 


> SSLUnitTestCase testsuite failures when using the IBM JVM
> ---------------------------------------------------------
>
>                 Key: JBAS-3570
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3570
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Test Suite
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: IBM 1.4.2 JDK
> RHEL 4, Linux Kernel 2.6.9
> Arch: i386
>            Reporter: Matt Wringe
>         Attachments: tomcat-ssl.log
>
>
> The org.jboss.test.web.test.ssl.SSLUnitTestCase tests fail when the IBM JDK is used.
> testHttpRedirect
> Error:	Connection refused
> testHttpRedirectSecurityDomain
> Error:	Connection refused
> testHttps
> Error:	Connection refused
> testHttpsSecurityDomain	
> Error:	Connection refused
> Stack Trace:
> java.net.ConnectException: Connection refused
> 	at java.net.PlainSocketImpl.socketConnect(Native Method)
> 	at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:336)
> 	at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:201)
> 	at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:188)
> 	at java.net.Socket.connect(Socket.java:478)
> 	at java.net.Socket.connect(Socket.java:428)
> 	at java.net.Socket.<init>(Socket.java:335)
> 	at java.net.Socket.<init>(Socket.java:150)
> 	at com.ibm.jsse.bv.<init>(Unknown Source)
> 	at com.ibm.jsse.JSSESocketFactory.createSocket(Unknown Source)
> 	at org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.createSocket(SSLProtocolSocketFactory.java:93)
> 	at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:652)
> 	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:628)
> 	at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497)
> 	at org.jboss.test.web.test.ssl.SSLUnitTestCase.doHttps(SSLUnitTestCase.java:117)
> 	at org.jboss.test.web.test.ssl.SSLUnitTestCase.testHttpsSecurityDomain(SSLUnitTestCase.java:85)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira