Hi all,
I'm currently working with soapUI-3.6.1 and everything is running smoothly. Today I've tried soapUI-4.0-beta2 and I encounter a bug :
11:20:23,913 INFO [DefaultSoapUICore] Creating new settings at [/path/soapui-settings.xml]
11:20:25,008 INFO [WorkspaceImpl] Loading workspace from [/path/default-soapui-workspace.xml]
11:20:25,163 INFO [WsdlProject] Loaded project from [file:/path/to/project/soapui-project.xml]
11:20:25,491 INFO [SoapUI] Used java version: 1.6.0_25
Exception in thread "XpcMessageLoop" java.lang.NullPointerException
at com.teamdev.xpcom.Xpcom.isMozillaThread(Unknown Source)
at com.teamdev.xpcom.a.b.a.a.<init>(Unknown Source)
at com.teamdev.xpcom.XpcMessageLoop.<init>(Unknown Source)
at com.teamdev.xpcom.XpcMessageLoop.getInstance(Unknown Source)
at com.teamdev.xpcom.b$a.run(Unknown Source)
The steps to reproduce are simple :
- download soapUI-4.0-beta2
- run /path/to/soapui/bin/soapui.sh
The interface shows up but it freezes as the bug occurs.
When I try to run soapUI-4.0-beta2 as root, the error is different ! See below :
11:20:35,022 INFO [DefaultSoapUICore] Creating new settings at [/root/soapui-settings.xml]
11:20:36,194 INFO [SoapUI] Used java version: 1.6.0_25
(process:20296): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.28.6/./gobject/gtype.c:2712: You forgot to call g_type_init()
(process:20296): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
(process:20296): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xa9370f51, pid=20296, tid=2905602928
#
# JRE version: 6.0_25-b06
# Java VM: Java HotSpot(TM) Server VM (20.0-b11 mixed mode linux-x86 )
# Problematic frame:
# C [libgconf-2.so.4+0x1ef51] __float128+0xe21
#
# An error report file with more information is saved as:
# /path/eviware/soapUI-4.0-beta2/bin/hs_err_pid20296.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
I've joined the file mentionned (hs_err_pid20296.log)
I have also tried with soap-UI-Pro-4.0.0-SNAPSHOT, I have the _exact same errors_
BTW I'm running Ubuntu 11.04 with classic interface.
Is this a bug in soapUI or a bug in my environnement ? The weird thing is that soapUI-3.6.1 works nice !
Cyril
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs (not used)"
File produced when soapUI is run as root
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs (not used)"
You need to disable jxbrowser component. If you are using soapui-pro.sh look for line with -Dsoapui.jxbrowser.disable=true and uncomment it.
If running from launcher, seek for *.vmoptions file in bin folder and add -Dsoapui.jxbrowser.disable=true .
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs (not used)"
Ok it seems to work now, but it is still a silly fix no ? Why does this happen ?
it is a third party component that have issues on linux. For me it works half time, half time not...so, this is a way to live with it..
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs (not used)"
Ok, should I close this bug ?
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs (not used)"
Last edit: Anonymous 2016-01-11
For me disabling jxbrowser in soapui.sh worked. When I changed *.vmoptions nothing changed.