SoapUI 5.6.0 won't start
Problem: I can't run SoapUI 5.6.0 on Linux. I see only splash screen, sometimes even the splash screen won't show up.I am using Ubuntu 20.04.1 LTS. It's newly installed. In the error.log is this exception: Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: 'boolean org.apache.xmlbeans.XmlOptionsBean.isLoadDTDGrammar()' at org.apache.xmlbeans.impl.common.SAXHelper.saxFactory(SAXHelper.java:70) at org.apache.xmlbeans.impl.common.SAXHelper.newXMLReader(SAXHelper.java:46) at org.apache.xmlbeans.impl.store.Locale.getSaxLoader(Locale.java:3066) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1272) at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:1259) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345) at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:252) at com.eviware.soapui.config.SoapuiSettingsDocumentConfig$Factory.parse(SoapuiSettingsDocumentConfig.java:59) at com.eviware.soapui.DefaultSoapUICore.initSettings(DefaultSoapUICore.java:259) at com.eviware.soapui.SwingSoapUICore.initSettings(SwingSoapUICore.java:99) at com.eviware.soapui.DefaultSoapUICore.init(DefaultSoapUICore.java:141) at com.eviware.soapui.StandaloneSoapUICore.<init>(StandaloneSoapUICore.java:38) at com.eviware.soapui.SoapUI$SoapUIRunner.run(SoapUI.java:791) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715) at java.base/java.security.AccessController.doPrivileged(AccessController.java:391) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90) I tried: - run an instance that I had on the previous OS (disk backup). - install new SoapUI 5.6.0 with installator that I newly downloaded. - remove all folders and setting files (default-soapui-workspace.xml, soapui-settings.xml, etc). - use previous backuped folders and setting files from an old OS instance. - use different versions of java (8 oracle ,11 openjdk ,13 oracle) - replace lib/xmlbeans-3.1.1-sb-fixed.jar with xmlbeans-3.1.0.jar nothing worksSolved4.7KViews0likes4CommentsSOAPUI_HOME environment variable ignored on Linux
Posting here since I couldn't find a place to file a bug. I would submit a pull request, but the contributor agreement seems like to too much bother for this type of change. I don't really expect to be doing other contributions. I'm using SoapUI-5.4.0 free edition on Centos 7.4 if anyone needs those details. There appears to be a bug in several of the shell scripts that basically ignore the SOAPUI_HOME environment variable. The script works if bash finds the script in the SoapUI bin directory. However, it does not work via a symbolic (or hard) link. Here's the environment. The variable points to the installed SoapUI. There is a symbolic link to the script I'm running and the link is in the path prior to the SoapUI bin directory. (Could also leave out the SoapUI bin directory) centos@icpclientaws ~]$ echo $SOAPUI_HOME /home/centos/soapui/SoapUI-5.4.0 [centos@icpclientaws ~]$ ls $SOAPUI_HOME JavaDoc.url RELEASENOTES.txt SmartBear License Terms of Use.txt jre licences uninstall README.md SmartBear License Terms of Use.md bin lib soapUI.url wsi-test-tools [centos@icpclientaws ~]$ ls -l ~/bin total 0 lrwxrwxrwx. 1 centos centos 50 Apr 25 15:53 testrunner.sh -> /home/centos/soapui/SoapUI-5.4.0/bin/testrunner.sh [centos@icpclientaws ~]$ echo $PATH /usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/centos/.local/bin:/home/centos/bin:/home/centos/soapui/SoapUI-5.4.0/bin The script fails to execute: [centos@icpclientaws ~]$ testrunner.sh /home/centos/bin/testrunner.sh: line 42: java: command not found ================================ = = SOAPUI_HOME = /home/centos = ================================ /home/centos/bin/testrunner.sh: line 70: java: command not found If I run testrunner.sh with shell debugging enabled, You can see SOAPUI_HOME is being overwritten with /home [centos@icpclientaws ~]$ echo $SOAPUI_HOME /home/centos/soapui/SoapUI-5.4.0 [centos@icpclientaws ~]$ sh -x testrunner.sh ++ dirname testrunner.sh + DIRNAME=. + cygwin=false + case "`uname`" in ++ uname + '[' -d /home/centos/soapui/SoapUI-5.4.0 ']' ++ cd ./.. ++ pwd + SOAPUI_HOME=/home + export SOAPUI_HOME + '[' -f /home/jre/bin/java ']' + '[' -f /home/../../PlugIns/jre.bundle/Contents/Home/jre/bin/java ']' + JAVA=java + SOAPUI_CLASSPATH='/home/bin/soapui-5.4.0.jar:/home/lib/*' ++ java -cp '/home/bin/soapui-5.4.0.jar:/home/lib/*' com.eviware.soapui.tools.JfxrtLocator /home/centos/soapui/SoapUI-5.4.0/bin/testrunner.sh: line 42: java: command not found + JFXRTPATH= + SOAPUI_CLASSPATH=':/home/bin/soapui-5.4.0.jar:/home/lib/*' + export SOAPUI_CLASSPATH + JAVA_OPTS='-Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/bin' + '[' /home '!=' '' ']' + JAVA_OPTS='-Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/bin -Dsoapui.ext.libraries=/home/bin/ext' + JAVA_OPTS='-Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/bin -Dsoapui.ext.libraries=/home/bin/ext -Dsoapui.ext.listeners=/home/bin/listeners' + JAVA_OPTS='-Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/bin -Dsoapui.ext.libraries=/home/bin/ext -Dsoapui.ext.listeners=/home/bin/listeners -Dsoapui.ext.actions=/home/bin/actions' + export JAVA_OPTS + false + echo ================================ ================================ + echo = = + echo = SOAPUI_HOME = /home = SOAPUI_HOME = /home + echo = = + echo ================================ ================================ + java -Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties -Dgroovy.source.encoding=iso-8859-1 -Dsoapui.home=/home/bin -Dsoapui.ext.libraries=/home/bin/ext -Dsoapui.ext.listeners=/home/bin/listeners -Dsoapui.ext.actions=/home/bin/actions -cp ':/home/bin/soapui-5.4.0.jar:/home/lib/*' com.eviware.soapui.tools.SoapUITestCaseRunner /home/centos/soapui/SoapUI-5.4.0/bin/testrunner.sh: line 70: java: command not found I can fix the issue by modifying the following section of the script # Setup SOAPUI_HOME if [ -d $SOAPUI_HOME ] then # get the full path (without any relative bits) SOAPUI_HOME=`cd $DIRNAME/..; pwd` fi Just change the if condition to the following (i.e. negate the condition). if [ ! -d $SOAPUI_HOME ] As written, the script is testing to see if there is a directory as SOAPUI_HOME and if there is, then it overwrites the SOAPUI_HOME variable (with garbage in my case). I doubt that this is the desired behavior. If it is, then I think some explaining comment would be in order. The following other scripts are also affected: loadtestrunner.sh mockservicerunner.sh toolrunner.sh soapui.sh I would appreciate it if someone could pass this along to the development team.1.9KViews0likes1CommentFreeze in OpenSUSE
I don't know why, but in OpenSUSE SOAPUI simply be freeze. Open App screen but if I try click in menus, nothing hapens!!! Any reason for that? Details about my enviroment: NAME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:42.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse"756Views0likes0Comments