search

flysa / log4jdbc

Automatically exported from code.google.com/p/log4jdbc
0 stars 0 forks source link

Cannot disable log4jdbc when using Logback #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The documentation states you should set a logger to FATAL to completely disable 
it, and disabling all 5 loggers will disable log4jdbc altogether (which would 
be a nice feature, by the way). However, Logback does not support the FATAL 
level.

What steps will reproduce the problem?
1. Use Logback as the logging backend (which is a natural choice if you use 
slf4j as your logging frontend).
2. Try to set a logger to FATAL – won’t work, default level used.

Original issue reported on code.google.com by MichaelPiefel on 29 Mar 2012 at 6:55

GoogleCodeExporter commented 8 years ago 
Yes, logback (and SLF4J) do not have FATAL.  The actual logic checks if any of 
the 5 loggers are at error level which implies error and below (error, info, 
debug, trace, etc.) So turning all the loggers OFF will have the same effect in 
logback or any other logging system.  I will make a minor change to the doc to 
make this a little more clear.

Original comment by arthur.b...@gmail.com on 29 Mar 2012 at 11:49