Forum Discussion
16 Replies
- richieCommunity Hero
Hi,
Erm.....if I understand correctly I think you're looking at this from the wrong perspective.
I don't believe this is a SoapUI issue.
SoapUI is only going to be able to provide any workable status response if the endpoint you have specified is correct. If it is correct then you need to consider logs, look at the RAW request and response etc. to work out what's going on.
SoapUI nor any tool I wouldn't have thought would be able to give you info indicating what is wrong with your endpoint if it is incorrect.
I'd double and triple check the endpoint is correct relative to what the client provided (as well as the security/authorization options) and if you're duplicating what was supplied, you need to go back to the client who setup the endpoint for you to ensure the endpoint is correct, message body is correct (if a POST/PATCH etc.) and the security creds/Authorization settings are correct.
I'd suggest checking your network settings - are you behind a firewall? can you only connect to the endpoint from within a specific domain? etc. - but I'd expect that you'd get something in your logs (destination host unreachable or permission denied etc.) if this was the case - hence the reason I'm leaning towards confirming the endpoint details with the 3rd party (but double check your settings first though!)
Perhaps someone else has some whizzy ideas to help - but I've got nothing!
Sorry I can't be of more help,
richie
- alphaackOccasional Contributor
Hello,
this is the only message/error i am seeing
- 2018-05-02 06:26:49.820 - Error getting response; javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Connection reset
- Bill_In_IrvineContributor
That error indicates you might not have the keystore set up for that endpoint.
You will need the private key and certificate of the endpoint and create a keystore - there are a lot of references and I forgot the one I used but I found one site
Once you make a keystore file you have to make ReadyAPI know about it. Here is a link for that
https://support.smartbear.com/readyapi/docs/projects/requests/ssl.html
- Bill_In_IrvineContributor
I was doing some looking. Perhaps the version of TLS is 1.0 on one and and 1.2 on the other.
see for example https://community.smartbear.com/t5/SoapUI-Open-Source/Solved-SSL-Handshake-exception-calling-a-secure-webservice/m-p/103595#M18090
Related Content
- 5 years ago
- 5 years ago
- 6 years ago