Eclipse Community Forums: EMF » [CDO] Remote unlocking mechanism changed

Help

Home

Home » Modeling » EMF » [CDO] Remote unlocking mechanism changed

Show: Today's Messages :: Show Polls :: Message Navigator

[CDO] Remote unlocking mechanism changed [message #1850255]

Wed, 23 February 2022 07:56

Robert Schulk

Messages: 144
Registered: July 2015

Senior Member

We are using durable cdo locks. These locks could be released on the server side via the InternalLockingManager:

      LockArea lockArea = lockManager.getLockArea(durableLockingID);
      lockArea.getLocks().clear();
      lockManager.updateLockArea(lockArea);

This seems to be not possible anymore with the newest build. Is there any alternative way to do it now, or did this get broken?

I also attached a test case (modified from LockingManagerRestartTransactionTest) which worked for CDO version 4.14.

Edit: this mechanism still works, but the currently open sessions will always see the object as locked. New sessions see the correct status.

Attachment: testCLearLocksOnServer.txt
(Size: 1.93KB, Downloaded 81 times)

[Updated on: Wed, 23 February 2022 13:06]

Report message to a moderator

Re: [CDO] Remote unlocking mechanism changed [message #1850355 is a reply to message #1850255]

Sat, 26 February 2022 03:12

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Hi Robert,

In the 4.16 cycle a complete overhaul of the locking mechanism was started with the goal of optimizing the prefetching and caching of lock states, see 4.16 Release Notes. In the 4.17 cycle there were more fundamental improvements/changes regarding locking, see 4.17 Release Notes.

I suspect that for lock state changes that are initiated in the server there are no notifications sent to the clients. Please submit a bugzilla and attach your test case.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator