Forum Discussion

powlhari's avatar
powlhari
New Contributor
12 years ago

java.util.concurrentmodificationexception:Document changed d

Hi,

when running testcases in parallel mode using batch file, java.util.concurrentmodificationexception:Document changed during select is thrown. Log doesnot show complete information on this exception.

the exception is thrown for any test cases in testsuite. how to fix this exception. and also want to know why this exception is thrown.

6 Replies

  • powlhari's avatar
    powlhari
    New Contributor
    thanks for the info. i did some research on the soapui api. i found that exception is thrown by xmlbeans. if any one can shed light on this xmlbean api and its usage in soapui test steps like (Transfer, PropertiesList).
  • Hi Team,

    We are also facing the same issue when we are running the test suites in parallel execution mode.
    The below error is occurred

    "java.util.ConcurrentModificationException: Document changed during select"

    Please let us know if this is a known issue with soapUI Pro- latest Version or we need to do any configuration settings to overcome this.

    Thanks,
    Manoj
  • powlhari's avatar
    powlhari
    New Contributor
    Below is the error log i could get when running load test for a single test case ( Total no of threads :60 duration:60s)

    The error occurs at Transfer step. is there any fix for this exception.

    java.util.ConcurrentModificationException: Document changed during select
    at org.apache.xmlbeans.impl.store.Path$XbeanPathEngine.next(Path.java:459)
    at org.apache.xmlbeans.impl.store.Cursor._toSelection(Cursor.java:931)
    at org.apache.xmlbeans.impl.store.Cursor._getSelectionCount(Cursor.java:946)
    at org.apache.xmlbeans.impl.store.Cursor.notifyChange(Cursor.java:882)
    at org.apache.xmlbeans.impl.store.Locale.notifyChange(Locale.java:1693)
    at org.apache.xmlbeans.impl.store.Cur.moveNode(Cur.java:1908)
    at org.apache.xmlbeans.impl.store.Cur.moveNode(Cur.java:1844)
    at org.apache.xmlbeans.impl.store.Cur.createHelper(Cur.java:287)
    at org.apache.xmlbeans.impl.store.Cur.createAttr(Cur.java:211)
    at org.apache.xmlbeans.impl.store.Locale.applyNamespaces(Locale.java:2282)
    at org.apache.xmlbeans.impl.store.Xobj.copy_contents_from(Xobj.java:2353)
    at org.apache.xmlbeans.impl.store.Xobj.copy(Xobj.java:2405)
    at org.apache.xmlbeans.impl.values.XmlObjectBase._copy(XmlObjectBase.java:155)
    at org.apache.xmlbeans.impl.values.XmlObjectBase._copy(XmlObjectBase.java:138)
    at org.apache.xmlbeans.impl.values.XmlObjectBase.copy(XmlObjectBase.java:119)
    at com.eviware.soapui.impl.wsdl.teststeps.PropertyTransfersTestStep$PropertyTransferResult.addTransferResult(PropertyTransfersTestStep.java:238)
    at com.eviware.soapui.impl.wsdl.teststeps.PropertyTransfersTestStep.run(PropertyTransfersTestStep.java:141)
    at com.eviware.soapui.impl.wsdl.teststeps.PropertyTransfersTestStep.run(PropertyTransfersTestStep.java:111)
    at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:238)
    at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
    at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:147)
    at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:42)
    at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
    at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner$InternalTestCaseRunner.run(WsdlLoadTestRunner.java:544)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
  • Hi guys,

    We haven't seen this before. I tried to analyse why you could be getting this, and to me it looks as if something in another thread is modifying the configuration of the property transfer itself while you are performing a property transfer. Could this be the case?

    Kind regards,
    Manne Fagerlind
    SmartBear Stockholm
  • powlhari's avatar
    powlhari
    New Contributor
    Hello,
    What I tried is, ran a test case having service call and property transfer and basic assertions with 40 threads in 60s. When I did the above running I got this error. If I remove property transfer step and run again, I am not getting this exception.