I have Ready! API 1.4.1 installed.
I have a rather large wsdl that I load with sample operations & requests. Regardless whether I create new or try to select an existing request, when I do my CPU pegs and it eventually returns but not for over 5 minutes or more.
Other test projects are fine.... something related to this larger WSDL ..
Hi Mcalvin,
You can try improving the memory usage in Ready! API. Please refer to this article to learn how to do this: http://readyapi.smartbear.com/soapui/working/improving_memory_usage
If this doesn’t help, I would suggest that you contact our Ready! API Support Team and let them know the WSDL URL (if possible) – they could investigate the situation and find a solution.
You might have to use the Deprecated SoapUI Pro version
I have NG Pro myself and the issue for some reason is this Citrix / Crazy Security / No permissions environment I have to deal with.
It seems to have something to do with the way resources are use, and/or Java.
I noticed if I keep Outlook closed - NG Pro works "ok" - but still the CPU clocks up high at times.
I tried everything and still I can't have Outlook open and use NG Pro - - NOR can I use extended desktop (can't explain that one - but it's linked to resources I'm sure)
Well for me / us the problem appears to lie in the very size and complexity of our wsdl. The free version of Soap UI does not demonstrate the issue but the Pro version does.
I am calling this a bug with Ready API for now. It simply cannot handle large and significantly complex wsdl's
Hi Mcalvin,
Could you please contact our Support Team (http://support.smartbear.com/product-list/ ) to investigate this behavior? If this is an issue in Ready! API, our Developers will try to fix this.
