Uploaded image for project: 'Publishing Transactional'
  1. Publishing Transactional
  2. EEPUBLISH-34

Concurrent publications of the same item can result into errors on commit / rollback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Neutral
    • None
    • None

    Description

      Steps to reproduce

      1.  Schedule two jobs to publish same tree at the same time

      Expected results

      1. No errors in logs, backup content is not overwritten

      Actual results

      1. Backup content is overwritten / lost for one of the pubications

      Workaround

      1. Schedule publications one after another to avoid concurrency issues

      Development notes

      This happens because backup content shares the same uuid / name and so when two publications of the same uuid / path come, the content in mgnlSystem workspace might get overwritten / removed by commit operation by one or the other publication.

      Ideally we should lock backup content until the transaction of publication item that arrived first is complete.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              dmaslanka Dominik Maslanka
              jsimak Jaroslav Simak
              Nucleus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Checklists

                  Bug DoR
                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 34m
                    34m