[jbossws-issues] [JBoss JIRA] (JBWS-3460) Investigate CXF specific tests IPv6 issues

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Fri Mar 16 09:53:47 EDT 2012


    [ https://issues.jboss.org/browse/JBWS-3460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677289#comment-12677289 ] 

Alessio Soldano commented on JBWS-3460:
---------------------------------------

Previously forgot about the JMS failures, hence I reopened.

The SOAP-over-JMS tests are passing here after having properly configured /etc/hosts. Basically, we need to avoid having hostnames bound to both ::1 and 127.0.0.1 .
                
> Investigate CXF specific tests IPv6 issues
> ------------------------------------------
>
>                 Key: JBWS-3460
>                 URL: https://issues.jboss.org/browse/JBWS-3460
>             Project: JBoss Web Services
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-4.0.2
>            Reporter: Richard Opalka
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-4.1
>
>         Attachments: patch-issue-30.txt
>
>
> There is a bunch of CXF tests that are failing when using IPv6 address:
> ---
> Tests in error: 
>   testWSDLHttpProxy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyWSDLTestCase): Unexpected end of file from server
>   testHttpProxy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyTestCase): Could not send Message.
>   testHttpProxyUsingHTTPClientPolicy(org.jboss.test.ws.jaxws.cxf.httpproxy.HTTPProxyTestCase): Could not send Message.
>   testSingleDeploy(org.jboss.test.ws.jaxws.cxf.bus.EJB3ClientBusTestCase): com.sun.xml.messaging.saaj.SOAPExceptionImpl
>   test(org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase): The specified request failed
> Tests run: 69, Failures: 0, Errors: 5, Skipped: 0
> ---
> Tests in error: 
>   testJMSEndpointClientSide(org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointOnlyDeploymentTestCase): javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed]
>   testMessagingClient(org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointOnlyDeploymentTestCase): Failed to create remoting connection
>   testJMSEndpointServerSide(org.jboss.test.ws.jaxws.cxf.jms_http.JMSHTTPEndpointDeploymentTestCase): Server returned HTTP response code: 500 for URL: http://[::1]:8080/jaxws-cxf-jms-http-deployment-test-servlet
>   testJMSEndpointClientSide(org.jboss.test.ws.jaxws.cxf.jms_http.JMSHTTPEndpointDeploymentTestCase): javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed]
> Tests run: 36, Failures: 0, Errors: 4, Skipped: 0

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossws-issues mailing list