Ticket #152 (new defect)
Concurrency error in managing monitors (ConcurrentModificationException)
| Reported by: | ddewaleffe | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Version: | 5.3 | Keywords: | |
| Cc: |
Description
Got the following trace while starting a test when the PTTMonitor had been stopped on the target host.
Starting local TestNode Starting local Monitor 2007-09-07 10:51:37,272 [main] DEBUG com.bitmechanic.maxq.Config - Generator: com.pushtotest.testmaker.gui.NewAgentWizard?.maxqhelp.TMCodeGenerator Proxy recorder server started on port: 8090 2007-09-07 10:51:37,647 [Thread-9] INFO com.bitmechanic.maxq.ProxyServer? - Proxy server started on port: 8090
- Validating test -
The test is valid.
- Test Resources -
XML Scenario: C:\Documents and Settings\ddw\projects\Cullen\SeleniumTests?\t1.xml Module File: file://C|/Documents and Settings/ddw/projects/Cullen/SeleniumTests/t1.py Module File: file://C|/Documents and Settings/ddw/projects/Cullen/SeleniumTests/loginlogout.py
- Loading Scenario -
The node localhost is valid The node localhost has loaded the scenario
- Starting Monitors -
Monitor for localhost started. The monitor on the Host (http://deployer.internal.denali.be) is not respoding
- Making Transactions -
- Restarting monitors -
Problem with monitor in host Recorder: java.util.ConcurrentModificationException? java.util.ConcurrentModificationException?
at java.util.AbstractList?$Itr.checkForComodification(AbstractList?.java:372) at java.util.AbstractList?$Itr.next(AbstractList?.java:343) at com.pushtotest.testmaker.XSTest.client.ControlRunner?.restartMonitor(ControlRunner?.java:1247) at com.pushtotest.testmaker.XSTest.client.ControlRunner?.run(ControlRunner?.java:477)
