[MAGNOLIA-1079] logging configuration doesn't survive magnolia restart Created: 25/Sep/06  Updated: 23/Jan/13  Resolved: 11/Dec/11

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0 RC2
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: John Mettraux Assignee: Fabrizio Giustina
Resolution: Won't Fix 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   

Changing the log4j log level for a package/set of packages seems not persisted.

If, for instance, "openwfe.org" is set to DEBUG, at Magnolia restart, it's back to WARN.

I didn't log out to test that, I did a shutdown/startup on the containing Tomcat.



 Comments   
Comment by Philipp Bracher [ 27/Sep/06 ]

This was intendet to be so. To change the configuration permanentely you need to change the log4j.xml file.

But the interface could get extended by a 'save' feature.

Comment by Boris Kraft [ 12/Oct/06 ]

Would you like to add a "save" button?

Comment by Fabrizio Giustina [ 11/Dec/11 ]

cleaning up: logging configuration in the webapp is never intended to be saved, it's useful at runtime for debugging but if you need to change it you have to edit the log4j.xml file.

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