how to make log.trace() work inside MBeans

[davekohr]

I'm using JBoss 3.2.3 and JDK 1.4.

For logging, I'm using org.apache.commons.logging.Log (in everything except MBeans) and org.jboss.logging.Logger (only in my MBeans--they use the inherited log field).

It seems as though log.trace() statements from org.apache.commons.logging.Log objects do show up as expected if and only if you set the logging threshold to "ALL" ("TRACE" works too) in the config file server/default/conf/log4j.xml. The log entries are marked as "DEBUG" level logging, but I can live with that. I think this is because log4j (the underlying log system) supports DEBUG but not TRACE level.

However, I can't get the log.trace() statements from my MBeans to show up, no matter what config I use. Does anyone know what I need to do to make these show up? Thanks.

[davekohr]

I spoke a bit too soon. trace.log() statements from org.apache.commons.logging.Log objects show up, even if you set the log level to DEBUG. This means I can't use them.... Does anyone know how to get trace() to work correctly?

[tsangcn]

Since JBoss is using Log4J for logging, org.apache.commons.logging.Log will use Log4J for logging too.

But Log4J defines priority (logging) levels : FATAL, ERROR, WARN, INFO, DEBUG.
While commons.logging defines logging levels: fatal, error, warn, info, debug, trace.

So the trace level is mapped to DEBUG.

See http://jakarta.apache.org/commons/logging/api/org/apache/commons/logging/impl/Log4JLogger.html#trace(java.lang.Object)

[davekohr]

Thanks. I knew log4j has DEBUG but not TRACE levels. I was hoping commons-logging provided some way to implement a TRACE level separate from the DEBUG level, but I guess it doesn't. Oh well.