[EEPUBLISH-34] Concurrent publications of the same item can result into errors on commit / rollback Created: 18/Feb/21  Updated: 20/Mar/23

Status: Open
Project: Publishing Transactional
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Dominik Maslanka
Resolution: Unresolved Votes: 0
Labels: backup
Remaining Estimate: Not Specified
Time Spent: 34m
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Maintenance of Publishing module
Team: Nucleus

 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.


Generated at Mon Feb 12 10:38:05 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.