Hi Ali,
depending on how much memory you have in your machine and how you use soapUI you could try to increase the settings in soapui.bat.. change the line
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx256m
to
for 1GB ram : set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx768m
for 2GB ram : set JAVA_OPTS=%JAVA_OPTS% -Xms768m -Xmx1500m
for 3GB ram : set JAVA_OPTS=%JAVA_OPTS% -Xms1024m -Xmx2500m
if you also run a lot of groovy scripts in load-tests you could add the following to the end of the line:
-XX:MaxPermSize=128m
or maybe
-XX:MaxPermSize=192m
Hopefully this helps, but it would be really good to know if there are any specific situations that seem to trigger this "behaviour".. and to see any strack-traces from the console window
Finally, it the problems persist, you could add the option
-XX:+HeapDumpOnOutOfMemoryError
to the above line, which will dump the heap to a log file when this happens, which you could mail to us..
I'll look at the autosave feature over the weekend!
regards,
/Ole
eviware.com