[PAGES-470] Concurrent creation of pages/components works only for the first user Created: 07/Jul/21  Updated: 02/Sep/21  Resolved: 24/Aug/21

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2.9
Fix Version/s: 6.2.11

Type: Bug Priority: Normal
Reporter: Mercedes Iruela Assignee: Roman Kovařík
Resolution: Fixed Votes: 2
Labels: maintenance, ui-team-support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File magnolia_6_2_11_test.mp4     File magnolia_6_2_11_test2.mp4    
Issue Links:
Problem/Incident
is caused by MAGNOLIA-7005 It's possible to create same name sib... Closed
Relates
causality
caused by PAGES-271 Aborting page properties dialog leave... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 35
Story Points: 5

 Description   

Steps to reproduce

  1. Log concurrently in Magnolia  Admincentral with to different sessions (for example, using two different browsers). https://demo.magnolia-cms.com/.magnolia/admincentral#app:pages-app:browser;/travel/::
  2. Click create a page
  3. Select Basic template
  4. When using different page names in different browsers, we hit an issue caused by PAGES-271. When using the same name, the issue is reproducible only on root, the other levels throw a repository exception.
  5. Click next.
  6. The ¡Page properties' dialog is opened, (optionally fill out the info) but do not save it yet.
  7. Go to the other browser, repeat steps 2], 3], 4], 5], 6]
  8. Save the dialog.
  9. Page is created in this browser.
  10. Go back to the first browser and save the 'Page properties' dialog.  

Expected results

Page is saved in JCR (shouldn't this fail with a page already exist message?)

Actual results

The dialog is closed, there is no new page created in Pages app, and there is no error.

Workaround

Development notes



 Comments   
Comment by Vincenzo Cerbone [ 15/Jul/21 ]

Is it sure that this bug is caused by MAGNOLIA-7005 ? This bug occurs also under other paths (not root only)!

Comment by wolf bubenik [ 26/Jul/21 ]

We reproduced this for 6.2.10. Simultanious adding of pages under same parent page fails.

  • Only one (first request?) page is created, all others got lost without any message.
  • Adding pages under different parents simultaniously works.

A related problem we have with paralell adding of components to an area:

  • only the first (fastest user) will be added, all other get an error message (component already exists)
Comment by Roman Kovařík [ 13/Aug/21 ]

Hello vincenzo.cerbone, wolf.bubenik

 

Creating pages on non root level results in javax.jcr.ItemExistsException: This node already exists: /travel/test for me. 

I can confirm on root level, the second user is silently ignored.

Update: so the difference is if we use different or same page names, updated the description.

 

Regards 

Roman

Comment by Vincenzo Cerbone [ 01/Sep/21 ]

Hi Roman,

unfortunately I can confirm the issue is still present on 6.2.11 when two users try to create a page on the same "level" (they are sibling).

This happens both on site root :
magnolia_6_2_11_test.mp4

as well as or any other sub-pages level:

magnolia_6_2_11_test2.mp4

This is a very critical issue for our clients because editorial concurrency (on the same "level" of the tree) happens on a daily basis. Silently ignoring the save action is not tolerable because the "failing" user will lose all his/her work : dialog closes without any help to recover working content.

 

Comment by Vincenzo Cerbone [ 02/Sep/21 ]

Hi Roman,

thanks very much for clarification. I tested latest dx-core 6.2.12 snapshot and it works like a charm on any "level" of concurrency.
When do you plan to officially release 6.2.12?

Regards

Vincenzo

Generated at Mon Feb 12 06:19:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.