-
Bug
-
Resolution: Won't Do
-
Neutral
-
None
-
4.4.1
-
None
The lock is used inconsistently and should be removed completely.
While the ExclusiveWriteLock is used in SaveHandlerImpl via which most of the content update is done, it is not used in other situations like updated done directly via JCR Tree or for meta data updates for example in InterceptFilter and in other places.
We should probably remove usage of the lock all together and deal with the concurrent updates when they happen to allow clustering on the author instance
Acceptance criteria
- is related to
-
-
- Closed
-
