Ошибка «Не удалось загрузить URL» SoapUI при загрузке WSDL
У меня возникают некоторые странные проблемы. Главное, что я продолжаю получать следующую ошибку при попытке добавить WSDL к новому проекту:
Error loading [https://. /token?wsdl]: java.lang.Exception: Failed to load url; https://. /token?wsdl, 0 - java.lang.Exception: Failed to load url; https://. /token?wsdl, 0 - at com.eviware.soapui.impl.wsdl.support.wsdl.UrlWsdlLoader.load(UrlWsdlLoader.java:184) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:121) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:226) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149) at java.lang.Thread.run(Unknown Source) Я подтвердил, что приложение на этом URL-адресе запущено и работает, и я могу попасть в WSDL из веб-браузера, но я продолжаю получать это сообщение об ошибке независимо от того, что. Я использую SoapUI 4.5.0 (32-бит) в окне Windows 7. Я также пробовал 64-битную версию с теми же результатами. Это происходит, будь то на VPN или нет. Знаете ли вы, почему я могу получить эту ошибку?
Issue
I keep having some weird problems. The main one is that I keep getting the following error when trying to add a WSDL to a new project:
Error loading [https://. /token?wsdl]: java.lang.Exception: Failed to load url; https://. /token?wsdl, 0 - Here’s the message recorded in the error.log file:
java.lang.Exception: Failed to load url; https://. /token?wsdl, 0 - at com.eviware.soapui.impl.wsdl.support.wsdl.UrlWsdlLoader.load(UrlWsdlLoader.java:184) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:121) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97) at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:226) at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46) at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149) at java.lang.Thread.run(Unknown Source) I verified that the application at that URL is up and running, and I can get to the WSDL from a web browser, but I keep getting this error message no matter what. I am using SoapUI 4.5.0 (32-bit) on a Windows 7 box. I’ve also tried the 64-bit version with the same results. It happens whether I am on VPN or not.
Do you know why I might be getting this error?
Solution
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.
Java lang exception soapui
SoapUI is a great tool for testing web services and works especially well with its automation features. I’ve been using this tool since as long as I can remember working in the IT industry, only recently moving some of the work over to newer tools like Postman. So even to this day SoapUI remains my primary testing tool. Unfortunately some time during the 5.2 release of SoapUI a number of plugins were installed that were meant for its Pro features, and now some of these plugins are incompatible with later versions of SoapUI and cause a number of exceptions to be logged while using the Test Runner.
The exception that is thrown is a ClassNotFoundException thrown when SoapUI is trying to load some of the plugins.
17:36:36,462 ERROR [SoapUI] An error occurred [com.eviware.soapui.plugins.auto.factories.AutoImportMethodFactory], see error log for details
Even though this exception looks menacing, the Test Runner is not adversely impacted. The tests run.
. and complete without issues.
Yet the logs are filled with these pesky exceptions. So what can be done about them? Simply put — don’t load those plugins! The plugins are found in the .soapuios/plugins directory under the home directory for the user (i.e. ~/ or C:\Users\ depending on your OS).
To disable loading of these plugins, rename the plugins directory to something like disabled_plugins. Easy. SoapUI will not be able to load these plugins now and the logs will no longer be filled with unnecessary exceptions!
Although I put in a great effort into researching all the topics I cover, mistakes can happen. Use of any information from my blog posts should be at own risk and I do not hold any liability towards any information misuse or damages caused by following any of my posts.
All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
NOTE: (2022) This Blog is no longer maintained and I will not be answering any emails or comments.
ORACLE SOA Blog — Concepts, Common Issues and Workaround
SOAPUI Error:
Error loading wsdl
There was something wrong with the wsdl you are trying to import
Error loading [https://host:port/tls12Tester/DIT?wsdl]: java.lang.Exception: Failed to load url; https://host:port/tls12Tester/DIT?wsdl, 0
2017-02-08 10:07:22,947 ERROR [errorlog] com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.makeInvalidDefinitionException(WsdlLoader.java:119)
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:112)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:488)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:477)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:94)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:209)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:131)
at java.lang.Thread.run(Unknown Source)
========================================================================
Root Cause:
Minimum security protocol version for webservice is set to TLS1.2
SSL.minimumProtocolVersion=TLSv1.2
========================================================================
How to verify:
1. Load wsdl in a browser to see if it’s loading fine or not.
2. use openssl to verify protocol,
openssl s_client -connect host:port -tls1_2
Result: Secure Renegotiation IS supported
SSL-Session:
Protocol : TLSv1.2
========================================================================
Resolution:
Edit SoapUI-5.2.1.vmoptions file located at C:\SmartBear\SoapUI-5.2.1\bin\SoapUI-5.2.1.vmoptions
Add the following parameter, save and exit.
-Dsoapui.https.protocols=TLSv1.2
Kindly note it will enable only TLSv1.2 protocol
Close and reopen SoapUI for changes to take effect.
Retry to load wsdl in SoapUI. This time it should work fine.