[PUBLISHING-60] App (and Server) crashed when publish a child item of an unpublished parent folder Created: 25/Jun/19  Updated: 29/Mar/22  Resolved: 05/Aug/19

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Quach Hao Thien Assignee: Quach Hao Thien
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File app_cannot_be_opened_on_first_click.log.txt     Text File threaddump-1561437718696.txt    
Issue Links:
supersession
is superseded by PUBLISHING-61 Endless loop when publishing node wit... Closed
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
Sprint: Declarative REST 3
Story Points: 5
Team: Nucleus

 Description   

Reproduce:

  1. Open Security app 
  2. Add new folder
  3. Add new user in just created folder
  4. Click on Publish button on the sidebar
  5. App crashed, and check the log

Problem found on Security app and Site Definition app.

 

For more information:

  • The Pages app disables the Publish button if the parent folder was unpublished.
  • Meanwhile, the Stories app allows user to click Publish, but the error message displays on the screen then, and app is still working.
  • The instance is broken with this crash, restarting Tomcat does not help.
    • Need to kill it before restarting. Maybe because when the instance get in this lock state, it can’t release repository lock so it can’t be stopped normally

 



 Comments   
Comment by Quach Hao Thien [ 05/Aug/19 ]

this bug has been fixed in https://jira.magnolia-cms.com/browse/PUBLISHING-61

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