Concurrent access on IOrderedCollection will lead to crash (same key already exist exception)


IOrderedCollection is mapped in the IOG as key value. When two threads add an entity to the same IOrderedCollection at the same time the id will be the same, because the id is based on the max id + 1 in the collection.

Possible solution: thread-safe SequentialIdGenerator should be used, and must generate an unique sequential id. Implementation and unit test (separate test program) attached.

file attachments