loadui not advancing past splash screen

Hello!

There might have been a regressed bug. But before we investigate that further, please try to use the latest nightly build of loadUI and make sure that you have tried the things on the installation troubleshooting page.

Regards

Henrik
SmartBear Software

Exact same issue here. Loaded once correctly (from SOAPUI) but now can't get past the splash screen. I have applied last night's build. Really stuck here!

Mac OSX 10.6.8
Java Web Start, VM, etc. 13.6.0

I see the instruction to uninstall and reinstall java web start on the installation issues topic page, but there are no instructions for the Mac environment. I am happy to try this but I would need to know the equivalent steps in OSX/UNIX in order to try it.

Smartbear, any input for us? Dead in the water and need to use the tool. Thanks.

Hi!

This is how you enable the Java Console on MacOS: [link]

We really need the output of that console to help you.


Thanks

Henrik
SmartBear Software

Thanks Henrik -
I enabled the console and I do see some warnings. Perhaps they will point you in the right direction. Here's the output during startup (ending with the display of the "permanent" splash screen). Let me know what my next step should be. Thanks!

----------------------------------------------------
Launching loadUI Build: loadUI-Dist-2011-06-13-[3] 2011/06/13 20:56
Configuring log4j from [/Applications/loadUI/soapui-log4j.xml]
08:47:39,090 WARN [SoapUI] Missing folder [/Applications/loadUI/./ext] for external libraries
08:47:39,277 INFO [DefaultSoapUICore] initialized soapui-settings from [/Users/edward/soapui-settings.xml]
08:47:39,615 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [/Applications/eviware/soapUI-Pro-4.0.0.app/Contents/Resources/app/bin/scripts]
08:47:39,934 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xop.xsd with targetNamespace http://www.w3.org/2004/08/xop/include
08:47:39,975 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/XMLSchema.xsd with targetNamespace http://www.w3.org/2001/XMLSchema
08:47:39,976 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xml.xsd with targetNamespace http://www.w3.org/XML/1998/namespace
08:47:39,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
08:47:39,978 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200505.xsd with targetNamespace http://www.w3.org/2005/05/xmlmime
08:47:39,979 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200411.xsd with targetNamespace http://www.w3.org/2004/11/xmlmime
08:47:39,981 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope.xsd with targetNamespace http://schemas.xmlsoap.org/soap/envelope/
08:47:39,987 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding.xsd with targetNamespace http://schemas.xmlsoap.org/soap/encoding/
08:47:39,990 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope12.xsd with targetNamespace http://www.w3.org/2003/05/soap-envelope
08:47:39,996 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.
log4j:WARN No appenders could be found for logger (org.springframework.osgi.extender.internal.activator.ContextLoaderListener).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
-> Framework started!

The fix suggested in this topic seems to have corrected the issue: http://www.eviware.com/forum/viewtopic.php?f=10&t=11585. I dropped the specified file into the same folder where my loadUI.command resides and can now launch LoadUI either by double-clicking on loadUI.command or from SOAPUI. It was necessary to rename the file, of course, as described in the post. The splashscreen persists for quite awhile (1 minute or so) but then it loads to the LoadUI workspace.

SmartBear, it looks like this file should be added to the installer - ?

THanks guys - I have been running with the Windows (eek!) version for the interim just to get my proof of concept moving forward. I will have a crack at what have been trying and let you know how I go.

Cheers

Ben

bensullivan wrote:
THanks guys - I have been running with the Windows (eek!) version for the interim just to get my proof of concept moving forward. I will have a crack at what have been trying and let you know how I go.n

I'm crossing my fingers for you!

Henrik
SmartBear Software