If I have in my logger configs:
Using "ALL" as my log level for hibernate. Hibernate uses jboss-logging. Jboss-logging just recently added support for Log4j2 (see version 3.2 - https://issues.jboss.org/browse/JBLOGGING-95). However, I'm using 3.1.4 currently which ends up then using the log4j 1.2 bridge so:
I noticed some Hibernate code failing checking the logger level such as:
Looking into this, it checks the loggers effective level against the passed in level. So in this case the loggers effective level should be ALL which should include TRACE. However, in the log4 1.2 bridge Category.getEffectiveLevel() doesn't have a case statement for ALL so it ends up defaulting to OFF:
Here's the JBoss logging check for reference - https://github.com/jboss-logging/jboss-logging/blob/master/src/main/java/org/jboss/logging/Log4jLogger.java#L36
The first conditional will be true but the second will be false due to the issue of mapping the ALL level.