code.onehippo.org is currently readonly. We are migrating to code.bloomreach.com, please continue working there on Monday 14/12. See: https://docs.bloomreach.com/display/engineering/GitLab

  • Ard Schrijvers's avatar
    REPO-1915 Make sure to have latest jcr node states instead of possibly stale nodes · 075c95c1
    Ard Schrijvers authored
    Since the lock via the LockManager does not involve any jcr locking, it
    does *never* trigger a cluster sync. This means that we can get the lock
    for a node that has been processed and finished just by another cluster
    node that also already freed the lock again. Making sure that after we
    obtained the lock to invoke a session refresh should result in that
    #isPendingTrigger returns false if another cluster node already did
    process the job.
    075c95c1
Name
Last commit
Last update
api Loading commit data...
builtin Loading commit data...
config Loading commit data...
connector Loading commit data...
dependencies Loading commit data...
deprecated Loading commit data...
engine Loading commit data...
jaxrs Loading commit data...
mockutils Loading commit data...
modules Loading commit data...
provider Loading commit data...
resources Loading commit data...
scripts Loading commit data...
servlets Loading commit data...
test Loading commit data...
testcontent Loading commit data...
testutils Loading commit data...
upgrade Loading commit data...
utilities Loading commit data...
workflow Loading commit data...
.gitignore Loading commit data...
LICENSE Loading commit data...
NOTICE Loading commit data...
README Loading commit data...
pom.xml Loading commit data...