[MAGNOLIA-2019] deactivation: node is not locked Created: 24/Jan/08  Updated: 23/Jan/13  Resolved: 24/Jan/08

Status: Closed
Project: Magnolia
Component/s: activation
Affects Version/s: 3.5.3
Fix Version/s: 3.5.4

Type: Bug Priority: Major
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
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
Date of First Response:

 Description   

there are several issues:

  • getNode() does not consider the fact that the new header transports a uuid (so no node returned)
  • as most log messages are not set to debug level we have never noticed that
  • the jcr session is logged out before we release the lock


 Comments   
Comment by Philipp Bracher [ 24/Jan/08 ]

And the old 3.0 protocol is not supperted

Comment by Philipp Bracher [ 24/Jan/08 ]

Any error message is not transported to the user

Generated at Mon Feb 12 03:32:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.