SoapUI (GUI and testrunner) initialize for more than 30 seconds
Below You can find logs from SoapUI GUI: Tue Sep 05 11:45:07 CEST 2017:INFO:Adding [S:\aut_api\lib\sqljdbc.jar] to extensions classpath Tue Sep 05 11:45:08 CEST 2017:INFO:initialized soapui-settings from [C:\Users\...\soapui-settings.xml] Tue Sep 05 11:45:39 CEST 2017:INFO:0 plugins loaded in 1 ms and testrunner: C:\Users\...\>rem ********* run soapui testcase runner *********** C:\Users\...\>"D:\SoapUI-5.3.0\bin\..\jre\bin\java" -Xms128m -Xmx1024m -Dsoapui.properties=soapui.properties "-Dsoapui.home=D:\SoapUI-5.3.0\bin\\" -Dsoapui.ext.libraries="D:\SoapUI-5.3.0\bin\ext" -Dsoapui.ext.listeners="D:\SoapUI-5.3.0\bin\listeners" -Dsoapui.ext.actions="D:\SoapUI-5.3.0\bin\actions" -Dsoapui.jxbrowser.disable=true com.eviware.soapui.tools.SoapUITestCaseRunner -r -a -c "ACD1" -t "S:\aut_api\MW\soapui-settings.xml" "S:\aut_api\MW\MW-AB.xml" -PsENV=TST SoapUI 5.3.0 TestCase Runner 11:41:16,562 INFO [SoapUI] Adding [D:\SoapUI-5.3.0\bin\ext\json.jar] to extensions classpath 11:41:16,564 INFO [SoapUI] Adding [D:\SoapUI-5.3.0\bin\ext\postgresql-8.4-703.jdbc4.jar] to extensions classpath 11:41:16,565 INFO [SoapUI] Adding [D:\SoapUI-5.3.0\bin\ext\sqljdbc.jar] to extensions classpath 11:41:17,077 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\...\soapui-settings.xml] SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 11:41:47,949 INFO [PluginManager] 0 plugins loaded in 3 ms 11:41:47,950 INFO [DefaultSoapUICore] All plugins loaded As you can see i both cases time consumed for parsing soapui-settings.xml or something which is done in beetween takes more than 30 seconds, and this is not acceptable. I have tried many things (java version , java memory tuning, different soapui-settings.xml location, ... and many more) but end up with nothing. Please advise what can be the cause. In Win7 everything works fine. The problem accures only on Windows Server 2012 R2.