|Re: [CDO] Concurrent accesses and ObjectNotFoundException [message #1699541 is a reply to message #1699077]
||Wed, 24 June 2015 22:13
| Stephane Fournier
Registered: July 2009
Thanks for your explanations.
I've just discovered the serializeCommits settings on server side.
To work with CDOMergingConflictREsolver, is it recommended to set it to true on server side with a mem store bad server ?
Eike Stepper wrote on Sat, 20 June 2015 08:18
Am 20.06.2015 um 10:01 schrieb Stephane Fournier:
> Hi Eike,
> thanks again for your quick answer.
> I have already experiences how to lock objects with CDOAutoLocker handler but I don't know how to do quite the same
> thing at read time without explicitly doing :
> CDOLock cdoReadLock = company.cdoReadLock();
> everywhere in the application code.
Locking is a pretty heavy mechanism in terms of signaling, too. Maybe you're better of by expecting respective
exceptions and handling them more gracefully, e.g. do the read again.
> By the way, if client A (JVM 1) uses CDOAutoLocker whereas client B (JVM 2) holds a ReadLock, client A trying to
> modify the same objects, will be blocked in the CDOAutoLocker until the client B has released its READ Lock ?
> What happens if the client B JVM crashes ? the read lock is stil there ?
No, all locks are owned by the locking view/transaction and are released when that view/transaction is closed (for
Please note that especially in this area I fixed some bugs for CDO 4.4.
Powered by FUDForum
. Page generated in 0.01760 seconds