Uploaded image for project: 'PUBLIC - Liferay Sync'
  1. PUBLIC - Liferay Sync
  2. SYNC-1447

Data isn't rolled back if exception happens mid transaction

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Connector-3.0.0
    • Fix Version/s: Connector-3.0.1
    • Component/s: Sync Connector
    • Labels:
      None

      Description

      We turn off transaction for batched requests because it may lock the tables up for too long. As a result of this, transactions aren't rolled back and data becomes out of sync.

      An example would be where a file is moved to the recycle bin and an exception occurs (after). The document remains in the trash but the SyncDLObject may not have updated. The expected outcome would be the transaction is rolled back and the document is "restored" from the trash.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 41 weeks, 6 days ago

                Packages

                Version Package
                Connector-3.0.1