Errors when saving our project

Hi!

Does this error occur when saving or loading the project?

regards!

/Ole
eviware.com

Hi Ole,

Both actually. It can load the project, but it omits the file that won't save (so it won't even load the previously saved version) and the same error message appears in the SOAP UI log.

I tried cloning the test case to another project and working on it there, which seemed fine, and it saved ok. But when cloned back to the original project it still won't save or load.

The only way I have been able to get the test case I want back into the correct project, is to create the project again from scratch. So all test suites were cloned to a new project and all project properties were set-up again.

This is now working fine in the new project, but we are still really concerned about why it happened as we lost a lot of work and have spent a day or so recovering it. We really don't want this to happen again but don't know how to avoid it.

Any ideas?

Thanks

Nicole

Hi,

We still have no idea why this issue occurred, but I am now having problems launching SOAP UI Pro. I'm getting a java heap space error just trying to open the application.

Do you know why this might be happening and how I can resolve it? I would also be keen to know how to avoid it in future.

Thank you

Nicole

Hello,

In directory where you installed soapUI Pro look in folder bin for file soapUI-Pro*.vmoptions and try changing values for Xmx and Xms ( try increasing it ). Save and restart soapUI.
Regarding errors with composite project what exactly were errors? Also, in global settings ( UI Settings ) you can set backup directory. If it is set than you can instruct soapUI to save all projects there, too. And they will be saved as normal projects. Also you choose to use autosave or just backup on exit.

Hope this helps,
robert

Hi Robert,

SAVING A SOAP UI PROJECT
The error message for saving is shown in the 1st post. It seems that the test case which is failing became corrupted, but we have no idea why. The only way around the issue was to go back to our version control software, retrieve an older copy, and clone it into a NEW project. Cloning it back into the existing project still caused it to corrupt and fail save when we made changes. It doesn't matter here whether we trigger the save or whether it is an auto save, either way, the file corrupted and we lost some work. The file was only 600kb in size but when we made a few small changes it became over 1mb in size and then would never re-load. But when we took an older version and cloned it into a new project, it remained within 700kb even after our changes. So something odd occured.

OPENING SOAP UI WITH A LARGE PROJECT SIZE
The error message for opening SOAP UI Pro was a java heap space error. I was able to open SOAP UI Pro as long as I removed the non-composite project causing the problems from the directory. Then it will open because it can't find the project, but will obviously show a failed project in the navigator window. The project we created was 164mb so I'm guessing this is too large for SOAP UI? What are your limits?

GROOVY SCRIPT ASSERTION ISSUE
Also, I wrote a groovy script assertion the other day that was over 3000 lines long and that seemed to fail too. I could only keep the assertion if I split it inoto 2. What is the exact limit here and can it be changed? I was writing a switch statement, and now can't use a default as the switch statement is now across 2 assertions, so any values that exisit that are not in my statement will now not be picked up. So it's not ideal splitting it. Do you know a way around this?

EXISTING VMOPTIONS

-Xms128m
-Xmx1024m
-XX:MaxPermSize=256m

What would you recommend changing these to?

I hope this gives you more information and you are able to help.

Thank you

Nicole

The limitations on size in SoapUI are the result of the Java VM implementation, and the computer setup that is is running on, so we cannot give you any hard limits.

In order to make your current setup run better, we do have a couple of suggestions:

1) Change the Xmx value to be higher (we recommend starting with 2048, but you can make it even higher if you need to)
2) For the groovy assertion, try putting most of the code in the script library, and call it from there, that should make things more stable


/Nenad
http://eviware.com

Hi,

Happy new year!

Thanks for your reply. We weren't able to change our Xmx settings to 2048 but that may be due to having an old version of soapUi Pro. We are currently on 3.5, but are now downloading 3.6.1. Hoepfully this will help and will enable us to make this change.

Could you please provide more details regarding how we might call our assertions from the script library. Do we need to completely rewrite them, or is there a process we can follow that enables us to keep most of the script intact? Some examples of this (using a simple script assertion) would be really helpful.

Thank you

Nicole

What happens when you try to set Xmx to 2048? It is a setting for the JVM, and the soapUI version really should make no difference.

As for the script library, you would have to create a groovy class with the assertion functionality (most likely you could cut and paste most of the code directly), and then put that class in the script library, and just call it from the groovy assertion.

For more information about working with the Script Library, you can check the following link:
http://www.soapui.org/Scripting-Propert ... brary.html

/Nenad
http://eviware.com