ServiceMix already includes commons-logging / log4j, so the SU will use these jars instead. This means that you should configure your log level in conf/log4j.xml. If you use a self-first class loader delegation you *may* be able to change that. But changing the log level in the default configuration is the easiest way i think. You can change it at runtime, as the file is parsed every minute for changes.
On 5/17/07, Atul From Infosys <[EMAIL PROTECTED]> wrote:
hi, i want to configure log4j at serviceunit level. i am using apache common-logging api. i package log4j.xml and common-logging.properties in su root directory and i have them mentioned in classpath of su as well. SA containing su gets deployed successfully, but no logging happens.. could you pls suggest any thing else to be done. Thanks. Atul -- View this message in context: http://www.nabble.com/configuring-log4j-for-su-level-tf3774402s12049.html#a10672480 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
