Bug 109873 – Log4j level adjuster should preserve changes across restarts

Bug 109873 - Log4j level adjuster should preserve changes across restarts

Summary:	Log4j level adjuster should preserve changes across restarts

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Web Application Framework
Classification:	Retired
Component:	other (Show other bugs)
Sub Component:
Version:	nightly
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	ccm-bugs-list
QA Contact:	Jon Orris
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-11-12 11:35 EST by Daniel Berrange
Modified:	2007-04-18 12:59 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-09-02 13:28:41 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Daniel Berrange 2003-11-12 11:35:03 EST

Description of problem:

When debugging a problem it is common to use the log4j level adjuster
to change the logging priorities of a number of categories. A
developer may then make some code changes, re-deploy & restart the
server. At which point they have to change all the log4j levels again.
This cycle may repeat several times. What is needed is for changes
made to log4j levels to be persisted across server restarts, although
probably only when the 'debugMode' flag is set to true.

Comment 1 Daniel Berrange 2006-09-02 13:28:41 EDT

Closing old tickets

Note You need to log in before you can comment on or make changes to this bug.