Forum Discussion

alexsoapui's avatar
alexsoapui
14 years ago

SoapUI 4.5 beta issue

Hi All,

I have downloaded the new version of SoapUI and I've tried to run my tests I used to do on version 4.0.1. For my surprise, I had the following error when trying to send a request to HTTPS endpoint. HTTP requests are fine. Is this an issue or a only a tool misconfiguration.

Thanks,
Alexandre

Thu Mar 01 12:21:39 CST 2012:ERROR:javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at sun.security.ssl.SSLSessionImpl.getPeerCertificates(Unknown Source)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:390)
at com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager$SoapUIClientConnectionOperator.openConnection(SoapUIMultiThreadedHttpConnectionManager.java:299)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:561)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:219)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:329)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:250)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

*Moved to beta forum // Henrik, SmartBear *
  • Pebblybeachbum's avatar
    Pebblybeachbum
    New Contributor
    14 years ago
    I have exactly the same issue

    Hopefully this will be addressed as a matter of priority, it makes testing impossible
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    14 years ago
    Hi,

    Thanks for reporting. We are looking at this (issue no. SOAPUI-3625).

    Regards

    Henrik, SmartBear
  • ixhussa's avatar
    ixhussa
    New Contributor
    13 years ago
    I'm getting the same error and similar behavior using Soap UI 4.5 Build Date 2012/03/26 16:10. (Win32)

    Under 4.0.1:
    I have a request that works against 4 different svc endpoints.

    Under 4.5:
    The exact same project/request works for 2 out of the 4 svc endpoints. The other 2 come up with the error noted in this thread.

    For now- I will continue to use v4.01 as primary but continue to play around with v4.5. Also I assume the project xmls are seamlessly compatible between the 2 versions?

    Is there a work around for this until the issue/ bug is resolved?

    Thanks in advance.
  • ixhussa's avatar
    ixhussa
    New Contributor
    13 years ago
    One more data point:

    I downloaded the most recent build (Build Date 2012/04/21 00:05) to see if it resolves the issue - Negative. Same behavior.
  • ixhussa's avatar
    ixhussa
    New Contributor
    13 years ago
    And one more data point:

    I attempted a work around. The 4 svc endpoints I was testing against all use different certs which were contained in one keystore that I had configured. I isolated the certs for the 2 svc endpoints that were problematic and added them to a new keystore. I then added this keystore to the project configuration and tested again - No joy.

    So I'm back to using v4.01 until a fix or work around reveals itself