Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-5654

Rollbacks can cause the ContentTracker and CascadeTracker to lose work

    Details

      Description

      SEARCH-243 changed the CommitTracker so that it only acquired locks for the AclTracker and MetaDataTracker before committing and rollback. This allowed the CommitTracker to move forward with commits without needing to acquire the locks for the ContentTracker and the CascadeTracker.

      While this decreased the amount of time the CommitTracker spent acquiring locks, it introduced a bug during rollbacks. The specific bug is that the ContentTracker and CascadeTracker can lose work during the rollback because they are not locked and their state is not reset following the rollback.

      This ticket will change the rollback behavior in the CommitTracker so that locks are acquired and state is reset for all trackers during a rollback.

      During a normal commit only the locks for AclTracker and MetaDataTracker will be acquired.

        Attachments

          Activity

            People

            • Assignee:
              closedissues Closed Issues
              Reporter:
              jbernstein Joel Bernstein [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: