Forum Discussion

Mason's avatar
Mason
Frequent Contributor
15 years ago

[RESOLVED] xPcom component fails to initiate in 3.0 beta 2009/06/23

Build 3.0-pro-daily-build-2009-06-23-[8], Build Date 2009/06/23 18:53

I am running in a 64bit OS.  This must be a recent change as the browser didn't fail to load with beta 2.

java.lang.Error: You cannot initialize Xpcom in this palatform. Supported only:
Intel 32 bit mode (x86 arch) use -d32 option,Sun(1.5 - 1.6) or Apple(1.5) Java
        at com.teamdev.xpcom.Xpcom.initialize(SourceFile:98)
        at com.teamdev.xpcom.Xpcom.initialize(SourceFile:79)
        at com.eviware.soapui.support.components.BrowserComponent.(Browser
Component.java:76)
        at com.eviware.soapui.ui.URLDesktopPanel.(URLDesktopPanel.java:33)

        at com.eviware.soapui.SoapUI.showPushPage(SoapUI.java:1051)
        at com.eviware.soapui.SoapUI$3.run(SoapUI.java:693)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)
java.lang.IllegalStateException: Message loop is not initialized. Please call in
itAWT() or initSWT() first
        at com.teamdev.xpcom.impl.F.h(SourceFile:28)
        at com.teamdev.xpcom.Xpcom.isEventDispatchThread(SourceFile:637)
        at com.teamdev.jxbrowser.impl.q.(SourceFile:43)
        at com.teamdev.jxbrowser.impl.u.a(SourceFile:6)
        at com.teamdev.jxbrowser.WebBrowserFactory.createBrowser(SourceFile:35)
        at com.eviware.soapui.support.components.BrowserComponent.initBrowser(Br
owserComponent.java:178)
        at com.eviware.soapui.support.components.BrowserComponent.getComponent(B
rowserComponent.java:107)
        at com.eviware.soapui.ui.URLDesktopPanel.(URLDesktopPanel.java:34)

        at com.eviware.soapui.SoapUI.showPushPage(SoapUI.java:1051)
        at com.eviware.soapui.SoapUI$3.run(SoapUI.java:693)
        at java.awt.event.InvocationEvent.dispatch(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

5 Replies

Sort By
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi,

    hmm.. is this with the bundled JRE or your own?

    regards,

    /Ole
    eviware.com
  • Mason's avatar
    Mason
    Frequent Contributor
    15 years ago
    I'm pretty sure this was a Java version that was on the system before SoapUI was installed.  Where does SoapUI install Java?

    java version "1.6.0_13"
    Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
    Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode)
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi!

    the installer puts it in the soapuipro\jre directory, but it isn't installed into your system. The browser component used by soapUI requires a 32-bit JRE so you can do one of the following:

    1) Use the JRE bundled with the installer
    2) Use a 32-bit JRE by yourself
    3) add the -d32 flag to the java options in the soapui.vmoptions / soapuipro.bat file
    4) disable the browser component by setting -Dsoapui.jxbrowser.disable=true on the commandline / in the vmoptions file..

    Hope this helps you forward!

    regards,

    /Ole
    eviware.com
  • Mason's avatar
    Mason
    Frequent Contributor
    15 years ago
    This only impacts use of the browser correct?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    15 years ago
    Hi!

    yes.. the rest of soapUI Pro will continue "as usual"

    The latest nightly build should detect a 64-bit JRE and disable the browser automatically though..

    regards!

    /Ole
    eviware.com