Forum Discussion
eelzinga
15 years agoOccasional Contributor
Yes i added that to the script.
the org/ietf/jgss/GSSException message got fixed by adding the rt.jar to the <loadui_home>/ext directory.
the next exception is still there
I guess when we run it from loadui the response payload of one of the soap steps is changed too quickly so we can't do the xpath on it to retrieve the 'id' of the record we should delete by use of the jdbc step.
The result is on a run of 60sec :
96 records created
58 record get deleted, and 38 are still in the database.
In soapui it works ok, also when i use the 'soapui' loadtest (both with 1 and for example 5 threads)
But when i trigger it from loadui it fails with the 'java.util.ConcurrentModificationException: Document changed during select' error.
the org/ietf/jgss/GSSException message got fixed by adding the rt.jar to the <loadui_home>/ext directory.
the next exception is still there
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
)
I guess when we run it from loadui the response payload of one of the soap steps is changed too quickly so we can't do the xpath on it to retrieve the 'id' of the record we should delete by use of the jdbc step.
The result is on a run of 60sec :
96 records created
58 record get deleted, and 38 are still in the database.
In soapui it works ok, also when i use the 'soapui' loadtest (both with 1 and for example 5 threads)
But when i trigger it from loadui it fails with the 'java.util.ConcurrentModificationException: Document changed during select' error.