ConcurrentModificationException when using the results of an index

[Sridhar Ramachandran]

Encountered a concurrent modification when multiple threads are accessing an index.

java.util.ConcurrentModificationException

        at java.util.LinkedList$ListItr.checkForComodification(Unknown Source)

        at java.util.LinkedList$ListItr.next(Unknown Source)

        at com.lambdazen.bitsy.util.BitsyElementIterator.hasNext(BitsyElementIterator.java:64)

        at com.tinkerpop.blueprints.util.wrappers.partition.PartitionVertexIterable$1.hasNext(PartitionVertexIterable.java:36)

        at java_util_Iterator$hasNext.call(Unknown Source)

[Sridhar Ramachandran]

Fixed in the 1.1-SNAPSHOT. Link to code changes

The collection returned by an index must be copied before returning to the caller, because subsequent commits from other threads will cause a ConcurrentModificationException to be thrown.