Forum Discussion

hbellur's avatar
14 years ago

LoadUI 1.5.1 Nightly build - Splash and freeze.

Hi,

We are facing a similar problem which has been mentioned by other members. LoadUI 1.5.1 (Nightly build) has been installed and when loading the LoadUI, the splash screen appears and freezes. Below is what is collected :

Java Web Start 1.6.0_25
Using JRE version 1.6.0_25-b06 Java HotSpot(TM) Client VM
User home directory = C:\Documents and Settings\<username>
----------------------------------------------------
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-2011-10-31-[2] 2011/10/31 03:13
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 [C:\LoaduiN\eviware\loadUI-1.5.1-SNAPSHOT\soapui-log4j.xml]
18:36:47,640 WARN [SoapUI] Missing folder [C:\LoaduiN\eviware\loadUI-1.5.1-SNAPSHOT\.\ext] for external libraries
18:36:47,640 INFO [DefaultSoapUICore] Creating new settings at [C:\Documents and Settings\<username>\soapui-settings.xml]
18:36:51,171 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [C:\LoaduiN\eviware\loadUI-1.5.1-SNAPSHOT\scripts]
18:36:52,656 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xop.xsd with targetNamespace http://www.w3.org/2004/08/xop/include
18:36:52,750 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/XMLSchema.xsd with targetNamespace http://www.w3.org/2001/XMLSchema
18:36:52,750 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xml.xsd with targetNamespace http://www.w3.org/XML/1998/namespace
18:36:52,750 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/swaref.xsd with targetNamespace http://ws-i.org/profiles/basic/1.1/xsd
18:36:52,750 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200505.xsd with targetNamespace http://www.w3.org/2005/05/xmlmime
18:36:52,750 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/xmime200411.xsd with targetNamespace http://www.w3.org/2004/11/xmlmime
18:36:52,765 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope.xsd with targetNamespace http://schemas.xmlsoap.org/soap/envelope/
18:36:52,765 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEncoding.xsd with targetNamespace http://schemas.xmlsoap.org/soap/encoding/
18:36:52,765 INFO [SchemaUtils] Added default schema from /com/eviware/soapui/resources/xsds/soapEnvelope12.xsd with targetNamespace http://www.w3.org/2003/05/soap-envelope
18:36:52,765 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!
Exception in thread "Awaiting Initialization" java.lang.RuntimeException: BundleContext is missing, has BeanInjector been configured?
at com.eviware.loadui.util.BeanInjector.getBean(BeanInjector.java:41)
at com.eviware.loadui.impl.dispatch.ExecutorManagerImpl$2.run(ExecutorManagerImpl.java:93)
at java.lang.Thread.run(Unknown Source)

Eager to use this tool but stuck badly on this problem. We faced this same problem on LoadUI 1.5 as well. Have tried all what has been mentioned in 'trouble shooting', but no luck.

Regards.

3 Replies

  • Hi!

    Strange. It kind of looks like you haven't installed loadUI in a new directory (not reusing a directory from any previous loadUI installation). Might this be the case?

    Best regards

    Henrik
    SmartBear Software
  • I have the same problem. No idea how to proceed.

    Fresh loadui installation (installed as root user into /opt directory).
    Notice: I first had to remove the packaged jre directory and change the startup script to use the jre of my machine (also Java 1.6 though) to get this far.
    Otherwise I would just see a Java webstart banner for a while, but nothing would happen. (Error encountered while invoking Java Web Start(execv): No such file or directory)

    I got it running on a CentOS VM now, but so far, trying to use LoadUI has been pretty frustrating for me...
  • dietervdw wrote:
    I have the same problem. No idea how to proceed.

    Hi!

    When you are writing that you have the same problem, do you mean that you also get a splash and freeze or do you actually get the exact same error message as the original poster? Are you also using a nightly build? From which date? Have you tried with the stable version?

    If you're not sure how to see the error messages, please read about it on this page.

    Regards

    Henrik
    SmartBear Software