[MAGNOLIA-3492] Reload of modules after activation results in exception due to misconfiguration Created: 06/Jan/11  Updated: 02/Jul/14  Resolved: 02/Jul/14

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.4.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Jan Haderka Assignee: Daniel Lipp
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
relation
is related to MAGNOLIA-3457 Config reload on Module doesn't work ... 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
Date of First Response:

 Description   

see the attached stacktrace for exception.
To reproduce:

  • download snapshot of CE bundle from hudson
  • install both author and public instances
  • try to activate config:/modules/dms including subpages.

Result:

  • activation proceeds
  • after reload of DMS on public, the exception is thrown


 Comments   
Comment by Jan Haderka [ 12/Jan/11 ]

Not reproducible with the build from hudson from Jan 12th

Comment by Jan Haderka [ 13/Jan/11 ]

the previous build of the 4.4.2-snapshot bundle has included the 4.4.1 binaries. Issue is reproducible with the 4.4.2-SNAPHOT binaries.

Comment by Jan Haderka [ 14/Jan/11 ]

The issue is caused by the fact that uuid of config node of the module is different between author and public and ModuleManagerImpl caches this node using LazyContentWrapper

Comment by Philipp Bärfuss [ 18/Jan/11 ]

We could fall back on the path if the uuid doesn't exist anymore (in the LazyContentWrapper).

Comment by Tobias Mattsson [ 20/Jan/11 ]

Added link to MAGNOLIA-3457 as it also concerns the Content object of the config node.

Comment by Jan Haderka [ 21/Jan/11 ]

Falling back on the path would break the contract of the uuid in LazyContentWrapper. Calling the getUUID() method would be no longer guarantied to return same value.
IMHO the proper solution is to have MMI taking care of the exception and flushing its node cache & reinitializing on the exception.

Comment by Daniel Lipp [ 02/Jul/14 ]

4.4.x is no longer supported - on 5.3 I wasn't able to reproduce hence I'm closing it as outdated.

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