Hi,
I've seem to come across some logging problems with cargo, or maybe it is because of maven.
Anyway. The core of the problem is that errors at the level of DEBUG does not print.
We have a log4j.properties file for our application that details the logging levels, and have an ConsoleAppender for its output. We use the commons-logging api in our application, and include log4j as its implementation to do the actual logging.
But cargo (or maven?) is overriding the log4j output. This is evident by seeing that FATAL and ERROR loglevels are rewritten to SEVERE. SEVERE is not a loglevel in log4j, and none of our log calls ever calls on this level. Also, we can see from the print output that it seems that cargo is wrapping its logging subsystem around the containers (tomcat). Something which is evident because our log output is prefixed with "[talledcontainer] if we do not specify the <log> or <output>.
If trying to set root loglevel in log4j to DEBUG we do not receive any debug output - only errors from INFO and up is written.
We are using Tomcat 5.5 as our container, with the latest cargo snapshot.
I suspect that cargo is calling setLoggingLevel or something equivalent, which is overriding log4j/commons-logging in the entire application. Could someone shed some light on how the logging subsystem in cargo works?
--
Alexander Brill
http://brill.no
