getting Error getting response; javax.net.ssl.SSLException: Couldn't kickstart handshaking
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
getting Error getting response; javax.net.ssl.SSLException: Couldn't kickstart handshaking
Hi All. When I'm trying to run Rest API call from readyAPI, I'm getting below error
Error getting response; javax.net.ssl.SSLException: Couldn't kickstart handshaking
I don't know what is the error here? I'm using ReadyAPI 3.1.0, same api is working fine in ReadyAPI 3.0.0
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Regards,
Rao.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi nmaro. My endpoint is looking fine. It has to be in the format of https://{ip-address}/service. Same endpoint was working fine earlier with version 3.1.0 also it is working fine in versions like 3.0.0
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Regards,
Rao.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
https://community.smartbear.com/t5/SoapUI-Open-Source/How-to-enable-TLS-1-2-in-SoapUI/td-p/96239
Regards,
Rao.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @arunbharath ,
Generally Handshake error occurs :
when there is difference in TLS of both application endpoint and soapui.
You can correct the version in .vmoptions file located in bin folder of your soapui
Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓
Thanks and Regards,
Himanshu Tayal
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi HimanshuTayal, Below is my .vmoption file contents, I'm not sure what to chage?
-XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=40 -Xms128m -Xmx8000m -Dsoapui.properties=soapui.properties -Dsoapui.home=C:\Program Files\SmartBear\ReadyAPI-3.1.0/bin -Dsoapui.ext.libraries=C:\Program Files\SmartBear\ReadyAPI-3.1.0/bin/ext -Dsoapui.ext.listeners=C:\Program Files\SmartBear\ReadyAPI-3.1.0/bin/listeners -Dsoapui.ext.actions=C:\Program Files\SmartBear\ReadyAPI-3.1.0/bin/actions -Dwsi.dir=C:\Program Files\SmartBear\ReadyAPI-3.1.0/wsi-test-tools -Djava.library.path=C:\Program Files\SmartBear\ReadyAPI-3.1.0/bin -Djava.util.Arrays.useLegacyMergeSort=true -Dsun.net.http.allowRestrictedHeaders=true -Djava.security.manager=com.smartbear.ready.ReadyApiSecurityManager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Add below in your .vmoption file
-Dsoapui.https.protocols=<TLSv1.2, TLSv1, SSLv3>
just specify single version which you want to use. Hope it will resolve your issue.
Click "Accept as Solution" if my answer has helped,
Remember to give "Kudos" 🙂 ↓↓↓↓↓
Thanks and Regards,
Himanshu Tayal
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@HimanshuTayal . Addding -Dsoapui.https.protocols=TLSv1.2 is resloved the ssl exception issue, but new problem is response is not showing up. Request went through successfully, even I'm able to see the response in the logs but not in the response panel.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which service REST or SOAP ? Have you looked at xml or json tabs?
Regards,
Rao.
