Forum Discussion

EBaethke's avatar
EBaethke
Contributor
12 years ago

[RESOLVED] UI Hangs in a Project with a large REST Service

Version: SoapUI Pro 4.5.2
OS: Windows 7 64-bit
Hardware: 3.20GHz quad-core CPU, 8.00GB RAM
---------------
I have a project with ~60 TestSuites and 4 WSDL services added.
The primary service is for REST and has approximately 300 Resources added

Symptoms:
- Whenever I double-click on a TestSuite, TestCase, or TestStep within my project, it takes about 1 minute to open. During this time the UI freezes and the mouse-pointer shows a loading icon.
- While its loading, the CPU usage for my computer will be maxed at 25% (i.e. one of the four cores is running at 100%)
This is incredibly frustrating and wastes a lot of time throughout the day.

Possible Cause:
I've found that removing the REST Service from the project will fix the freezing issues, and all TestSuite, TestCase, and TestSteps open instantaneously.
---------------

I searched all through the forums and tried suggestions here: http://www.soapui.org/Working-with-soapUI/improving-memory-usage.html for memory usage. This was the closest thing I could find to match the symptoms: http://www.soapui.org/forum/viewtopic.php?f=13&t=13256&p=32337&hilit=test+on+demand#p32337 but their solution does nothing for me.

Has anyone else experienced similar issues?
Does anyone know what SoapUI is doing during this time when it is hanging? Is it double-checking all the recources?
Is there a reason these resources cannot be cached or stored in memory in some way so they don't need to be loaded every time a TestSuite, Case, or Step is loaded?
Any suggestions would be greatly appreciated!

2 Replies

  • Have you tried loading the REST interface on its own and run test against it? Does it Work? Is there away for us to access the project so that we can do some further investigation?

    Regards,
    Temil
  • We have found out our problem.
    We removed <con:inferredSchema> ... </con:inferredSchema> from first project
    We removed a lot of <con:representation>...</con:representation> from second project
    We can now open faster (2 seconds versus 70 seconds) our projects / test suites / test cases without these invalid xml elements.