[MAGNOLIA-2743] startup: don't fail to start the system just because a single module/component fails to start Created: 25/May/09  Updated: 23/Jan/13  Resolved: 15/Jun/09

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 4.0.1
Fix Version/s: 4.1

Type: Improvement 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

Issue Links:
relation
is related to MAGNOLIA-2445 Error in install/update still allows ... Closed
is related to MAGNOLIA-2552 FactoryUtil: newInstance() method sho... Closed
is related to MAGNOLIA-2598 Module dependency issue should be dis... Closed
is related to MAGNOLIA-2711 Failure to resolve class when finishi... Closed
supersession
is superseded by MAGNOLIA-1670 Updatemech : review exception handlin... 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)
Date of First Response:

 Description   

Since FactoryUtil.newInstance() is re-throwing exceptions (MAGNOLIA-2552) a module or component startup can fail.
ModuleManager and Content2Bean itself should be aware of this and treat exceptions accordingly.



 Comments   
Comment by Philipp Bärfuss [ 25/May/09 ]

Since FactoryUtil.newInstance() is re-throwing exceptions a module or component startup can fail. Various places must be made aware of that fact:

  • ModuleManager
  • Content2Bean
Comment by Magnolia International [ 25/May/09 ]

MAGNOLIA-2445 is sort of related to this too (even though it seems to say the opposite)

Comment by Philipp Bärfuss [ 25/May/09 ]

MAGNOLIA-2445 is related to installation/update when having the magnolia.update.auto set to true.

The problem I run into is that the system was miss configured (well by some install tasks but the install did not fail at all). That went as far as that a single miss configured command stopped the system to start up.

Comment by Magnolia International [ 29/May/09 ]

Partly fixed in 4.1 RC1; will review before final - and either leave as it or push the issue to 4.1.1 if needed.

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