Given:
JBoss 6 M3 Application Server
$ ls -la $JBOSS_HOME/common/lib/slf4j-* -rwx------+ common/lib/slf4j-api.jar -rwx------+ common/lib/slf4j-jboss-logmanager.jar
I believe the libraries above provide a bridge between SLF4J and the JBoss logging system.
My web application relies on SLF4J for logging. Although, I am not packing any slf4j libs with my WAR.
$ jar tvf proj-web/target/proj.war | grep slf4 $
(If I turn them on, it doesn't matter)
My jboss-logging.xml set the level for the CONSOLE handler to DEBUG
$ more server/default/deploy/jboss-logging.xml ... <console-handler name="CONSOLE" autoflush="true" target="System.out"> <error-manager> <only-once/> </error-manager> <level name="DEBUG"/>
Question:
What did I forget to get in my JBoss logging protocol? I do not even see TRACE that it is trying to bind the JBoss Logging system to SLF4J .
===== [UPDATE] =====
It really works !! (no additional configuration)
I just changed my code from logger.debug("abc") to logger.info("xyz") , and now I have log output.
=> So, it looks like I just can't get the right filtering at the log level ... [to be continued]
source share