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
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
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.
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.
