Title: Long transactions and optimistic locks

I am attempting to read an object structure from Thread-A, modify it, and update the full structure using a call to the long transaction update( ) method.  In the meantime, Thead-B queries for a read-only object which happens to be referenced in the object structure known by Thread-A.  Neither thread is updating this object, but I still get a Timestamp Mismatch error on the update of the object structure.

The class mapping for the read-only object is marked access="read-only".  I'm not sure what else to configure to tell the optimistic locking mechanism not to be concerned with this object.

Thanks for any advice,
David

Reply via email to