El-Jodi
16 days agoOccasional Contributor
AbstractTestRunner error
Hi folks,
since version 3.59.0 we are experiencing the following error message running our test via gilab within the rapi docker image:
ERROR [AbstractTestRunner] Exception during Test Execution
org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider com.sun.org.apache.xerces.internal.parsers.XIncludeAwareParserConfiguration could not be instantiated: java.lang.IllegalAccessException: class org.apache.xerces.parsers.ObjectFactory cannot access class com.sun.org.apache.xerces.internal.parsers.XIncludeAwareParserConfiguration (in module java.xml) because module java.xml does not export com.sun.org.apache.xerces.internal.parsers to unnamed module @2b62475a
at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source) ~[xercesImpl-2.9.1.jar:?]
at com.eviware.soapui.support.jdbc.JdbcUtils.createResultSetHolder(JdbcUtils.java:162) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcResponse.<init>(JdbcResponse.java:48) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.createResponse(JdbcSubmit.java:371) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.runQuery(JdbcSubmit.java:187) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.run(JdbcSubmit.java:158) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.<init>(JdbcSubmit.java:90) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.ProJdbcSubmit.<init>(ProJdbcSubmit.java:12) ~[ready-api-soapui-pro-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.panels.teststeps.ProJdbcRequest.submit(ProJdbcRequest.java:15) ~[ready-api-soapui-pro-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.run(JdbcRequestTestStep.java:238) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:311) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:56) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:192) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:117) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) ~[ready-api-soapui-3.59.0.jar:3.59.0]
at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:142) [ready-api-soapui-3.59.0.jar:3.59.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]
running the same tests using the docker image with version 3.57.0 doesn't throw the error. Has anybody experienced something similar?
Thanks for your support in advance.
Regards
El-Jodi