|
| Re: [CDO] Locking in 4.x [message #717199 is a reply to message #717170] |
Fri, 19 August 2011 14:58  |
|
Hi Cyril,
Caspar has just committed a huge patch related to locking and there are also some new locking features pending (also
related to locking in offline clones). Unfortunately he cannot easily follow the newsgroup so I suggest that you submit
a bugzilla to discuss the issues you outlined.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 19.08.2011 15:53, schrieb Cyril Jaquier:
> Hi all,
>
> I have checked out the code from trunk at revision 8924 because we would
> like to use the new client-side CDOIDs (UUID) in order to drop one of
> our own patch that remapped the IDs during a branch switch.
>
> When I start the server (only the master), I get several times the
> following exception:
>
> org.eclipse.emf.cdo.common.util.CDOException: Cannot unlock in a
> non-local branch when clone is not connected to master
> at
> org.eclipse.emf.cdo.internal.server.syncing.SynchronizableRepository.unlock(SynchronizableRepository.java:502)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.UnlockObjectsIndication.indicating(UnlockObjectsIndication.java:60)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndication.indicating(CDOServerIndication.java:84)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedInput(IndicationWithResponse.java:90)
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:326)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:63)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerWriteIndication.execute(CDOServerWriteIndication.java:39)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
>
> As this exception seems to disappear after a while, is this critical or
> just a temporary failure?
>
> I can start a client and connect but during a rollback I get the
> following exception:
>
> java.lang.IllegalStateException: Durable locking is not enabled.
> at
> org.eclipse.emf.cdo.internal.server.syncing.SynchronizableRepository.unlockThrough(SynchronizableRepository.java:517)
> at
> org.eclipse.emf.cdo.internal.server.syncing.SynchronizableRepository.unlock(SynchronizableRepository.java:505)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.UnlockObjectsIndication.indicating(UnlockObjectsIndication.java:60)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndication.indicating(CDOServerIndication.java:84)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedInput(IndicationWithResponse.java:90)
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:326)
> at
> org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:63)
> at
> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerWriteIndication.execute(CDOServerWriteIndication.java:39)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
>
> Indeed, durable locking is not enabled and I don't see any reason to
> enable it because as far as I know we never used any locking mechanism
> provided by CDO. Do I need to set something to completely disable locking?
>
> Thank you.
>
> Cheers,
> Cyril
>
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02651 seconds
] 
Search
Help
Register
Login
Home
