Bug 114831

Summary:	Production install should come with a log4j.properties in the config directory
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Daniel Berrangé <berrange>
Component:	installation	Assignee:	Dennis Gregorovic <dgregor>
Status:	CLOSED WONTFIX	QA Contact:	Jon Orris <jorris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	nightly
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-03-17 16:47:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Berrangé 2004-02-03 13:05:13 UTC

Description of problem:
The default log4.properties file for production installations is
hidden away inside the JAR for CCM-Core. This makes it practically
impossible for novice users to figure out how to alter the debugging
levels & this makes remote diagnosis for PS teams very difficult. Thus
we should deploy the core log4j.properties file as a plain file to
somewhere likle /etc/ccm/conf and ensure that this directory comes
first in the CLASSPATH.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dennis Gregorovic 2004-02-04 06:27:00 UTC

@40036

Comment 2 Dennis Gregorovic 2005-03-17 16:47:30 UTC

closing old tickets