LoadUI Project Corrupted (Windows 7)

Update: Java Console Output:

Java Web Start 1.6.0_25
Using JRE version 1.6.0_27-b07 Java HotSpot(TM) Client VM
User home directory = C:\Users\sergeydeg
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
m: print memory usage
o: trigger logging
p: reload proxy configuration
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
0-5: set trace level to <n>
----------------------------------------------------
Launching loadUI Build: loadUI-Dist-2011-06-13-[3] 2011/06/13 20:56
log4j:WARN No appenders could be found for logger (com.eviware.loadui.fx.WindowControllerImpl).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Configuring log4j from [E:\WinApps\loadUI-1.5.0\soapui-log4j.xml]
14:58:05,058 WARN [SoapUI] Missing folder [E:\WinApps\loadUI-1.5.0\.\ext] for external libraries
14:58:05,620 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\sergeydeg\soapui-settings.xml]
14:58:06,462 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [E:\WinApps\loadUI-1.5.0\scripts]
14:58:06,908 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xop.xsd with targetNamespace http://www.w3.org/2004/08/xop/include
14:58:06,972 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/XMLSchema.xsd with targetNamespace http://www.w3.org/2001/XMLSchema
14:58:06,976 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xml.xsd with targetNamespace http://www.w3.org/XML/1998/namespace
14:58:06,977 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/swaref.xsd with targetNamespace http://ws-i.org/profiles/basic/1.1/xsd
14:58:06,979 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200505.xsd with targetNamespace http://www.w3.org/2005/05/xmlmime
14:58:06,980 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200411.xsd with targetNamespace http://www.w3.org/2004/11/xmlmime
14:58:06,982 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope.xsd with targetNamespace http://schemas.xmlsoap.org/soap/envelope/
14:58:06,988 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding.xsd with targetNamespace http://schemas.xmlsoap.org/soap/encoding/
14:58:06,989 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope12.xsd with targetNamespace http://www.w3.org/2003/05/soap-envelope
14:58:06,994 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding12.xsd with targetNamespace http://www.w3.org/2003/05/soap-encoding
ShellTUI: No standard input...exiting.
-> Framework started!
14:59:03,687 INFO [WsdlProject] Loaded project from [file:/C:/Users/sergeydeg/Documents/VNR-soapui-project.xml]
14:59:04,008 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [E:\WinApps\loadUI-1.5.0\scripts]
14:59:04,435 INFO [DefaultSoapUICore] Importing preferences from [C:\Users\sergeydeg\soapui-settings.xml]
14:59:04,439 INFO [HttpClientSupport$Helper] Updating keyStore..

Hello,

I have never heard of this problem. Would it be possible for you to send a corrupted project to us? Please send it to support@eviware.com and refer to this topic.

Thanks in advance!

Henrik
SmartBear Software

Has this issue been resolved at all/is there a known workaround for fixing the corruption?

I had two loadUI project files go corrupt yesterday. The second of these was created from the first by using the Save As Copy functionality. I then opened that project and made changes to it. While it was open, I also changed the soapUI project that contains the test cases that both loadUI projects call into to add test case parameters for the web service endpoints that the soapUI test needs to call so that I can pass these in from my loadUI test.

I then closed the second loadUI project to switch to the first one. I got an error about the file being corrupt and loadUI asked if I'd like to remove 'null' from the workspace. I got the same error when trying to reopen the second project.

Could changing the soapUI project to add extra test case parameters have resulted in loadUI being unable to load the loadUI project?

Hello,

This hasn't been solved yet. Can you send your projects to smartbear-sweden-support@smartbear.com
so we can test them and try to recover them?

regards!
Predrag
SmartBear Software

Has this problem been solved yet?

Hi,

Sorry for the late response. I'm working on it at the moment and the
problem is I can't reproduce it. It would be great if you could send me
some corrupted project so i can try it.

regards!
Predrag
SmartBear Software

Hello everyone,

This should be fixed now. Please download the latest nightly build and try it.

regards!
Predrag
SmartBear Software

Thank you for fixing the "corrupted file" problem. However, something else 'got broken' *I think* because of this fix... transferring properties from SOAPUI testcase doesn't seem to work anymore. What I am doing is running a load test based on a SOAPUI project and transferring some properties so that I can view them in the Output Table while I am in LoadUI.. this helps me keep track my requests.

This problem has not been solved. I downloaded the latest nightly builds for both SoapUI and LoadUI and checked out my soapUI project to make sure all the test cases ran properly. They ran fine under SoapUI and then I created a project under LoadUI to generate load against 4 test cases from the same SoapUI project and it ran fine there too. I saved the project and exited LoadUI. When I restarted LoadUI and attempted to reload the project, it gave me the project corruption error. I then removed the corrupted project and exited LoadUI and then restarted LoadUI to make sure everything was "clean". Once LoadUI was back up, I recreated the same project as I had before, referencing the same SoapUI project as before as well. I DID NOT run the test after it was created but instead simply saved the project and exited. I wanted to see if running the project could have been creating the problem or even updating the SoapUI project AFTER the LoadUI project had been created. My first attempt was to just reopen the LoadUI project without doing anything to the project in SoapUI and without having even run it in LoadUI. When I attempted to open the project in LoadUI, it gave me the corrupted project error. Again, all I did was create the project and save it, close LoadUI, restart LoadUI, and then try to reopen the project I just created. I sent an email to the support email address along with the corrupted project in a zip file for analysis. This has become a very frustrating bug and I hope someone is looking into the cause and a resolution.

Hi Jay,

We answered your e-mail that you sent to support saying we need your soapUI project as well to fully test it. But by just closing the loadUI dialog saying that the soapUI project is missing (see quote below), everything loads fine on my computer with loadUI 1.5.1-SNAPSHOT (the public nightly build).

Specified soapUI project file C:\COS\Testing\AMLoadTestProject-soapui-project.xml does not exist. File may have been moved, renamed or deleted.

Regards

Henrik
SmartBear Software