Bug 114831 - Production install should come with a log4j.properties in the config directory
Summary: Production install should come with a log4j.properties in the config directory
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dennis Gregorovic
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-03 13:05 UTC by Daniel Berrangé
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-03-17 16:47:30 UTC
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.