I did a little more research and determined that the act of iterating over a
collection in two separate threads is not enough to cause a
ConcurrentModificationException, unless the iterator removes items from the
collection.
This leads me to conclude that something must have changed in OpenJUMP's
code since Pedro filed his bug report last May. I've poured over the stack
trace in the bug report and the code itself, and after talking with Larry
can't determine what would now cause this exception to be thrown.
I suppose it is possible, though not likely, that the JVM implementation
Pedro was using may not have properly implemented the correct behavior in
this case and threw the exception when the collection was iterated over by
two threads.
I will close this bug report on SourceForge. It has been a short and painful
journey, but I have learned alot.
I want to especially thank Larry for all of his help with this. My thanks to
David at Vivid Solutions as well.
The Sunburned Surveyor
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
