Hi, On Fri, Jan 27, 2012 at 9:50 AM, Berry van Halderen <[email protected]> wrote: > Before a JCR save action, the journal table in the database is > consulted. If there are logged actions performed by other Jackrabbit > instances in the cluster than these actions are imported/replayed first > (SharedItemStateManager.doExternalUpdate). Then the actual changes > are written to the database. Where this fails, it that in between the > check for external updates and actually writing stuff into the database, > there might actually be update performed by another Jackrabbit instance.
That shouldn't be possible since the first cluster node should be holding the cluster lock during the entire "update-persist" operation. Thus another cluster node shouldn't be able to make any concurrent changes. BR, Jukka Zitting
