cancel
Showing results for 
Search instead for 
Did you mean: 

SSLExceptions in SOAPUI NG via ReadyApi v1.5

New Contributor

SSLExceptions in SOAPUI NG via ReadyApi v1.5

When using SoapUI NG Pro in ReadyApi v1.5, I am getting an SSLException connecting to web services using https.  But, when I test the same service using earlier versions of SoapUI, it works.  

 

Here is the exception I'm getting using SoapUI NG Pro in ReadyApi v1.5:

 

ERROR:javax.net.ssl.SSLException: Received fatal alert: close_notify
javax.net.ssl.SSLException: Received fatal alert: close_notify
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
at sun.security.ssl.AppOutputStream.write(Unknown Source)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:159)
at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:179)
at org.apache.http.impl.conn.LoggingSessionOutputBuffer.write(LoggingSessionOutputBuffer.java:73)
at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:115)
at org.apache.http.entity.ByteArrayEntity.writeTo(ByteArrayEntity.java:110)
at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:89)
at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:117)
at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:265)
at org.apache.http.impl.conn.AbstractClientConnAdapter.sendRequestEntity(AbstractClientConnAdapter.java:231)
at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:236)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.doSendRequest(HttpClientSupport.java:119)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:682)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:486)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:295)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:225)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119)
at java.util.concurrent.Executors$RunnableAdapter.call(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)

 

As a workaround, I can perform the following steps:

 

Add the following lines to: C:\Program Files\SmartBear\ReadyAPI-X.X.X\bin\ReadyAPI-X.X.X.vmoptions
-Dsoapui.https.protocols=TLSv1,TLSv1.1,TLSv1.2,SSLv2Hello,SSLv3
-Dsoapui.https.ciphers=SSL_RSA_WITH_RC4_128_MD5
-Dsun.security.ssl.allowUnsafeRenegotiation=true

 

Open C:\Program Files\SmartBear\ ReadyAPI-X.X.X \jre\lib\security\java.security
Comment out the line:
jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768

After I save the changes, and reopen ReadyApi I am able to connect to the service successfully.

 

Can anyone tell me what specifically has changed in the newer versions of SoapUI that would make the https connections fail?   Are there other ways to fix this issue besides editing the vmoptions and java.security files?  Or, are there plans to address this in the next release?

 

Thanks!

3 REPLIES 3
Community Manager

Re: SSLExceptions in SOAPUI NG via ReadyApi v1.5

Hi Jon_S,

 

We’ve just released a new version of Ready! API – v. 1.6. Could you please check if you get the same exception in this product version? You can download the installation file here:

https://support.smartbear.com/downloads/readyapi/

 

---------
Tanya Gorbunova
SmartBear Community Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.↓↓↓↓↓
New Contributor

Re: SSLExceptions in SOAPUI NG via ReadyApi v1.5

I updated to v1.6.  Unfortunately, the exception is still happening. 

Community Manager

Re: SSLExceptions in SOAPUI NG via ReadyApi v1.5

Hi Jon_S,

 

Sad to hear this Smiley Sad

In this case, could you please report this issue to our Ready! API Support Team? You can do this here: http://support.smartbear.com/product-list/

They will investigate the behavior and provide you with a solution.

---------
Tanya Gorbunova
SmartBear Community Manager

Did my reply answer your question? Give Kudos or Accept it as a Solution to help others.↓↓↓↓↓
New Here?
Join us and watch the welcome video: