Update mechanism improvements (MAGNOLIA-5529)

[MAGNOLIA-3576] Module startup failure should still start observation of that module, or stop it. Created: 02/Mar/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Sub-task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3457 Config reload on Module doesn't work ... Closed
Template:
Date of First Response:

 Description   

If a info.magnolia.module.ModuleLifecycle#start fails (with a RuntimeException of sorts), for instance because of a wrong configuration, the module should either be observed (so configuration can be fixed), or at least stopped (because some processes might have started). Or both?

Likewise, if c2b fails to initialize the module bean, it seems it's consequently not observed, so one can't fix the configuration without restarting.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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