Pax-Logging configuration

[David Savage]

Hi there,

I'm currently evaluating switching our internal log management code
over to use pax logging but I'm seeing some odd behaviour wrt j.u.l
handling and I wonder if it's a known problem or something I'm not
doing?

I've installed both the api and service bundles (version 1.4) and
started both early in our boot process and there are definitely no
other log providers around (except the j.u.l classes as they come from
the system classpath). I'm then using the OSGi ConfigManager to set
the following config options:

log4j.rootLogger=info,R
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.File=paremus.log
log4j.appender.R.MaxFileSize=100MB
log4j.appender.R.MaxBackupIndex=1
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n

Now when new bundles are installed it successfully redirects all
logging to paremus.log - except the j.u.l log. The j.u.l messages get
sent to the log file but also get dumped to the console - and it's the
console logging I'd like to clear up. During a quick browse of the
source I notice in the code that the j.u.l logging is intercepted by
adding a listener to the root ("") context - should this be sufficient
to intercept all logging?

Any help much appreciated.

Regards,

Dave

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general