[PUBLISHING-86] Provide an app to clear activation locks Created: 24/Aug/20  Updated: 29/Mar/22  Resolved: 09/Mar/21

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

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Jaroslav Simak
Resolution: Done Votes: 3
Labels: None
Remaining Estimate: 0d
Time Spent: 1.75d
Original Estimate: Not Specified

Issue Links:
Relates
causality
relation
is related to EEPUBLISH-28 Recurring Problem With Node Locking A... Closed
is related to PUBLISHING-99 Move away from JCR node locking Closed
is related to PUBLISHING-88 Keep track of lock owners with sessio... Closed
is related to MGNLSYNC-42 Synchronization manager does not comp... 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)
Documentation update required:
Yes
Date of First Response:
Epic Link: Support
Sprint: HL & LD 22, HL & LD 23, HL & LD 24
Story Points: 8
Team: Nucleus

 Description   

Since the introduction of the publishing modules we have seen some tickets coming through support where customers are unable to publish due to "locked nodes". It seems that we have two different kinds of locks.

  • The actual JCR lock that is applied to nodes when performing the activation.
    2020-08-21 11:20:22,923 DEBUG ional.receiver.locking.TransactionalJcrLockManager: About to begin publish of website:8fa4a73f-51c3-40ac-b698-715595216186:/travel/about/company
    2020-08-21 11:20:22,923 DEBUG ional.receiver.locking.TransactionalJcrLockManager: 376:1598001622918 Requesting XA lock
    2020-08-21 11:20:22,931 DEBUG info.magnolia.publishing.locking.JcrLockManager   : parent path:/travel/about/careers
    2020-08-21 11:20:23,007 DEBUG info.magnolia.publishing.locking.JcrLockManager   : session-admin-256 DID locked website:/travel/about/careers
      

It would be helpful to distinguish in the logs (both author and public) which kind of lock we are dealing with. One issue is an actual locked node where the other is more of a flag.

An improvement would be a way to clear these issues from the Publishing app. Right now I have statistics about publishing data and can see that errors have occurred (if any). But I have no way to take any action on those errors. With a lock management app I would have a way to inspect the current locks and a way to release them.


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