#46 ConcurrentModificationException in XdsTest

[Bill Majurski]

java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:782)
at java.util.ArrayList$Itr.next(ArrayList.java:754)
at gov.nist.toolkit.testengine.XdsTest.runAndReturnLogs(XdsTest.java:670)
at gov.nist.toolkit.testengine.Xdstest2.run(Xdstest2.java:306)
at gov.nist.toolkit.session.server.serviceManager.XdsTestServiceManager.runUtilityTest(XdsTestServiceManager.java:234)
at gov.nist.toolkit.session.server.serviceManager.XdsTestServiceManager.xdstest(XdsTestServiceManager.java:93)
at gov.nist.toolkit.session.server.services.SendDirect.run(SendDirect.java:85)
at gov.nist.toolkit.directsim.DirectServiceManager.directSend(DirectServiceManager.java:57)
at gov.nist.toolkit.xdstools2.server.ToolkitServiceImpl.directSend(ToolkitServiceImpl.java:106)

[Bill Majurski]

Problem is caused by different in UI and Session object handling: UI acts like each tab can support separate concurrent interaction while Session object is shared and can therefore only support single thread. The instance var transactionSettings is the cause of the problem.

Approach:
1) Make current transactionSettings into defaultTransactionSettings
2) Each request gets new copy initialized from default. Some vars (logRepository) do not convey.
3) Modify XdsTestServiceManager#runMesaTest and runUtilityTest to carry request specific copy as parameter.
4) Once it reaches PlanContext it is no longer a problem.