When running the same Open JPA 2.0 cache load test on two different cache providers, one of the providers makes the test prone to optimistic locking errors.
Can someone explain why using one provider results in optimistic locking errors while the other provider (default concurrent provider) has no such errors. Is performance of the cache provider a factor in this explanation ? I am trying to understand the relationship between optimistic lock violation and Cache Provider characteristics. Sample Exception --> <openjpa-2.0.0-SNAPSHOT-r422266:826665 nonfatal store error> org.apache.openjpa.util.OptimisticException: Optimistic locking errors were detected when flushing to the data store. The following objects may have been concurrently modified in another transaction: [org.apache.openjpa.persistence.datacache.common.apps.AttachE-156] --Thanks, Rohit Kelapure -- View this message in context: http://n2.nabble.com/Optimistic-locking-errors-cause-tp3858274p3858274.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
