You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2002/08/07 01:53:56 UTC
DO NOT REPLY [Bug 11512] New: -
Chainsaw forces output of its internal messages to console.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11512>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11512
Chainsaw forces output of its internal messages to console.
Summary: Chainsaw forces output of its internal messages to
console.
Product: Log4j
Version: 1.2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: mwomack@apache.org
Main.class contains the following method:
/** initialise log4j **/
private static void initLog4J() {
final Properties props = new Properties();
props.setProperty("log4j.rootCategory", "DEBUG, A1");
props.setProperty("log4j.appender.A1",
"org.apache.log4j.ConsoleAppender");
props.setProperty("log4j.appender.A1.layout",
"org.apache.log4j.TTCCLayout");
PropertyConfigurator.configure(props);
}
This forces all internal output to the console, disregarding any configuration
that may have been applied by the log4j.configuration property. Chris Bailey
has posted a message on the user list trying to find a way to turn this output
off. With the current code, he is stuck.
Suggested solution: Maybe the initLog4J() method should check for the
log4j.configuration property, and if it exists, do not apply any
configuration. If it does not exist, then apply the default configuration it
applies right now.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>