[MAGNOLIA-3466] Log errors at repo startup explicitly Created: 14/Dec/10  Updated: 19/Jan/11  Resolved: 20/Dec/10

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

Type: Improvement Priority: Neutral
Reporter: Jan Haderka Assignee: Magnolia International
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)
Date of First Response:

 Description   

Currently if there is an Error thrown during initialization (like class missing resulting in NoClassDefFoundException) while starting up the repo, this exception is swallowed silently. MgnlServletContextListener.startServer() should log all Throwable issues inside of the VoidOp execution instead of depending on the app server to log the problem (which doesn't always happen).



 Comments   
Comment by Magnolia International [ 14/Dec/10 ]

Arguably, this could simply be logged in info.magnolia.cms.beans.config.ConfigLoader#load with an extra catch block (which would let the exception bubble up of course)

Comment by Magnolia International [ 20/Dec/10 ]

committed a simple fix to 4.4 branch and trunk, adding a catch block in info.magnolia.cms.beans.config.ConfigLoader

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