SoapUI “failed to load url” error when loading WSDL

╄→гoц情女王★ 提交于 2019-12-02 21:49:09

I have had similar problems and worked around them by saving the WSDL locally. Don't forget to save any XSD files as well. You may need to edit the WSDL to specify an appropriate location for XSDs.

I have had the same problem. I resolved it by disabling the proxy in the SoapUI preferences. (source : http://www.eviware.com/forum/viewtopic.php?f=13&t=12460)

In my case the server were the service was installed was configured only for TLS. SSL was not allowed. So you have to update SoapUI vmoptions file by adding

-Dsoapui.https.protocols=TLSv1.2

You can find vmoptions file under SoapUI installation folder:

C:\Program Files (x86)\SmartBear\SoapUI-5.0.0\bin\soapUI-5.0.0.vmoptions

OR change your server setting to allow SSL

I got this error when trying to load a WebService implemented in MS Dynamics AX. Because I was connecting via VPN to my network, something went wrong with IPv6 settings. After googling, I found the solution here: http://support.microsoft.com/kb/929852

Hope this will help.

In my case the

 Error loading [https://.../token?wsdl]: java.lang.Exception: Failed to load url; https://.../token?wsdl, 0 

was caused by fake certificate. If you get the following in browser

"There is a problem with this website’s security certificate." 

this is the case.

The resolution was to import a certificate to

 C:\Program Files (x86)\SmartBear\SoapUI-5.0.0\jre\lib\security\cacerts 

Which is default java used by SOAPUI

Inside the wsdl file look for the import element, which looks like this :

`<import  namespace="nameSpaceValue" location="Users/myname/.../targetxsdName.xsd"/>`

Change the location attribute in the above element to the location of your xsd files stored locally, and it should work.

The following solution helped me:

-Djsse.enableSNIExtension=false

In SoapUI-5.3.0.vmoptions.

If you are running your Web Applicaiton with the default port of 8080, please try to change the port to some other value and run your applicaiton again and trigger again your SOAPUI request. As you might have history projects in your SOAP UI workspace with port number 8080, might create issues. Please try this might be helpful to you.

Regards, Ravi.

user5067156

This could be a problem with IPV6 address SOAP UI picking. Adding the following JVM option fixed it for me:

-Djava.net.preferIPv4Stack=true

I added it here:

C:\Program Files\SmartBear\soapUI-4.5.2\bin\soapUI-4.5.2.vmoptions

I had this issue when trying to use a SOCKS proxy. It appears that SoapUI does not support SOCKS proxys. I am using the Boomerang Chrome app instead.

My solution was to modify the java.security file:

\SoapUI-5.3.0\jre\lib\security\java.security

Comment code syntax:

#jdk.certpath.disabledAlgorithms=MD2, DSA, RSA keySize < 2048 #jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024

I had this error and in my case, the problem was that I was using "localhost" in the URL.
I resolved that changing the localhost word for the respective IP, (Windows + R -> cmd -> ipconfig) then read the IP and write it to the URL replacing the "localhost" word

Close and reopen soapui. Probably is a bug of the application

For java version above 1.8, Use below command to setup soapUI jar

java -jar --add-modules java.xml.bind --add-modules java.xml.ws

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!