You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Alison Ortega <ap...@gw.fis.NCSU.EDU> on 2003/06/09 18:25:11 UTC

log4j - category and appender questions

I am in the "figuring out how it works with weblogic" stage.
I have the following configured in my .lcf file:

log4j.rootCategory=, R
log4j.category.log=B1
log4j.appender.B1=org.apache.log4j.DailyRollingFileAppender
log4j.appender.R=org.apache.log4j.DailyRollingFileAppender
log4j.appender.B1.File=/local/logs/webappdv/logtest/logtest.log
log4j.appender.R.File=/local/logs/webappdv/logtest/logtest1.log
log4j.appender.B1.DatePattern='.'yyyy-MM-dd
log4j.appender.R.DatePattern='.'yyyy-MM-dd
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.B1.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=[slf5s.start]%d{DATE}[slf5s.DATE]%n%p[
slf5s.PRIORITY]%n%x[slf5s.NDC]%n%t[slf5s.THREAD]%n%c[slf5s.CATEGORY]%n%l[slf5s.L
OCATION]%n%m[slf5s.MESSAGE]%n%n
log4j.appender.B1.layout.ConversionPattern=[slf5s.start]%d{DATE}[slf5s.DATE]%n%p
[slf5s.PRIORITY]%n%x[slf5s.NDC]%n%t[slf5s.THREAD]%n%c[slf5s.CATEGORY]%n%l[slf5s.
LOCATION]%n%m[slf5s.MESSAGE]%n%n

log4j.appender.B1.MaxFileSize=10MB
log4j.appender.R.MaxFileSize=10MB
log4j.appender.B1.MaxBackupIndex=30
log4j.appender.R.MaxBackupIndex=30

and I configure by:
PropertyConfigurator.configure(logInitFile);
and obtain instances of loggers by
Logger.getLogger(this.class); or something to that effect.
I get the following when the configurator is run:
log4j: Parsing for [root] with value=[, R].
log4j: Parsing appender named "R".
log4j: Parsing layout options for "R".
log4j: Setting property [conversionPattern] to
[[slf5s.start]%d{DATE}[slf5s.DATE]%n%p[slf5s.PRIORITY]%n%x[slf5s.NDC]%n%t[slf5s.THREAD]%n%c[slf5s.CATEGORY]%n%l[slf5s.LOCATION]%n%m[slf5s.MESSAGE]%n%n].
log4j: End of parsing for "R".
log4j: Setting property [datePattern] to ['.'yyyy-MM-dd].
log4j: Setting property [file] to
[/local/logs/webappdv/logtest/logtest1.log].
log4j:WARN No such property [maxFileSize] in
org.apache.log4j.DailyRollingFileAppender.
log4j:WARN No such property [maxBackupIndex] in
org.apache.log4j.DailyRollingFileAppender.
log4j: setFile called: /local/logs/webappdv/logtest/logtest1.log, true
log4j: setFile ended
log4j: Appender [R] to be rolled at midnight.
log4j: Parsed "R" options.
log4j: Parsing for [log] with value=[B1].
log4j: Level token is [B1].
log4j: Category log set to DEBUG
log4j: Handling log4j.additivity.log=[null]
log4j: Finished configuring.

It appears as if the non-root appender is never completely configured,
but I can find no example of how to do it otherwise.  My log messages
always go to the root appender.  If I configure no root appender, I get
a warning.  
What I am trying to accomplish is to have one appender per application
(.war deployment in weblogic).
My fear is that you really only get one logger "configuration" per oc4j
container, which means that all appenders that I configure will get all
messages unless I implement filtering???
Any thoughts or suggestions would be greatly appreciated.

Alison Ortega
North Carolina State University
ACS 
Systems Programmer II
919-513-1417

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org