Forum Discussion
Pru_PLC_Support
15 years agoOccasional Contributor
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
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