16 years ago
ConcurrentModificationException in soap UI Mock
I'd first like to outline soapui is a great testing tool and thank eviware to provide the open source community with such a good tool. However, I currently have the issue described below.
I am using the war produced by the soapUI "mock as war" functionality as an endpoint for an application that I am load testing. This mock is deployed in a jetty server.
During this load test, to avoid soapUi to crash I send at regular interval the clear command via a wget call.
While monitoring the results in the UI I get regular instances of the following exception:
I believe there might be an issue in the way soap ui uses the commons collection.
Thanks for your help and sorry by advance if this issue was previously posted.
I am using the war produced by the soapUI "mock as war" functionality as an endpoint for an application that I am load testing. This mock is deployed in a jetty server.
During this load test, to avoid soapUi to crash I send at regular interval the clear command via a wget call.
While monitoring the results in the UI I get regular instances of the following exception:
HTTP ERROR 500
Problem accessing /voucherValidation.war/master. Reason:
INTERNAL_SERVER_ERROR
Caused by:
java.util.ConcurrentModificationException
at org.apache.commons.collections.list.TreeList$TreeListIterator.checkModCount(TreeList.java:828)
at org.apache.commons.collections.list.TreeList$TreeListIterator.next(TreeList.java:837)
at com.eviware.soapui.mockaswar.MockAsWarServlet.printMaster(MockAsWarServlet.java:368)
at com.eviware.soapui.mockaswar.MockAsWarServlet$MockServletSoapUICore.dispatchRequest(MockAsWarServlet.java:259)
at com.eviware.soapui.mockaswar.MockAsWarServlet.service(MockAsWarServlet.java:171)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:915)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:539)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
I believe there might be an issue in the way soap ui uses the commons collection.
Thanks for your help and sorry by advance if this issue was previously posted.