GPMONGODB-71: Optimistic locking exception in findBy/findAll methods

[graemerocher]

Original Reporter: danpolites
Environment: Ubuntu 11.04, Java 1.6
Version: 1.0.0.M6
Migrated From: http://jira.grails.org/browse/GPMONGODB-71

We've been experiencing optimistic locking exceptions on findAll/findBy methods. Are the objects being updated after findBy/findAll calls because there is no dirty checking taking place?

StackTrace Sanitizing stacktrace:
org.springframework.datastore.mapping.core.OptimisticLockingException: The instance was updated by another user while you were editing
at org.springframework.datastore.mapping.mongo.engine.MongoEntityPersister.checkVersion(MongoEntityPersister.java:419)
at org.springframework.datastore.mapping.mongo.engine.MongoEntityPersister$5.doInDB(MongoEntityPersister.java:400)
at org.springframework.data.document.mongodb.MongoTemplate.execute(MongoTemplate.java:293)
at org.springframework.datastore.mapping.mongo.engine.MongoEntityPersister.updateEntry(MongoEntityPersister.java:391)
at org.springframework.datastore.mapping.mongo.engine.MongoEntityPersister.updateEntry(MongoEntityPersister.java:69)
at org.springframework.datastore.mapping.engine.NativeEntryEntityPersister$2.run(NativeEntryEntityPersister.java:428)
at org.springframework.datastore.mapping.core.impl.PendingOperationExecution.executePendingInsert(PendingOperationExecution.java:32)

[graemerocher]

burtbeckwith said:
I can't replicate this, so it was either already fixed or the same issue as GPMONGODB-65