问题:

I'm currently observing that a 3rd party library (namely restfb) is using java.util.logging and I'm seeing those logs end up in STDOUT even though I don't have an SLF4J console appender configured in my logback.xml. I also have the jul-to-slf4j bridge in my classpath. Does the jul-to-slf4j bridge only log to the appenders configured by logback when the bridge is installed or does it also log to stdout?

回答1:

You need to call SLF4JBridgeHandler.install(). You also need to enable all log levels at the root logger (reason in excerpt below) in java.util.logging and remove the default console appender.

This handler will redirect jul logging to SLF4J. However, only logs enabled in j.u.l. will be redirected. For example, if a log statement invoking a j.u.l. logger disabled that statement, by definition, will not reach any SLF4JBridgeHandler instance and cannot be redirected.

The whole process can be accomplished like so

import java.util.logging.Logger; import org.slf4j.bridge.SLF4JBridgeHandler;  SLF4JBridgeHandler.removeHandlersForRootLogger(); SLF4JBridgeHandler.install(); Logger.getLogger("").setLevel(Level.FINEST); // Root logger, for example.

You can set the level to something higher than finest for performance reasons, but you won't be able to turn those logs on without enabling them in java.util.logging first (for the reason mentioned above in the excerpt).

回答2:

As mentioned in the javadocs for SLF4JBridgeHandler, you get either install SLF4JBridgeHandler programmatically by invoking:

 // Optionally remove existing handlers attached to j.u.l root logger  SLF4JBridgeHandler.removeHandlersForRootLogger();  // (since SLF4J 1.6.5)   // add SLF4JBridgeHandler to j.u.l's root logger, should be done once during  // the initialization phase of your application  SLF4JBridgeHandler.install();

or via logging.properties

 // register SLF4JBridgeHandler as handler for the j.u.l. root logger  handlers = org.slf4j.bridge.SLF4JBridgeHandler

As for performance, the section on jul-to-slf4j bridge discusses this issue. In essence, since you are already using logback, enabling the LevelChangePropagator should yield good performance regardless of the load.

回答3:

I use SLF4J and new Postgres driver 42.0.0

According changelog it use java.util.logging

To have driver logs it is enough:

Add jul-to-slf4j bridge:

org.slf4jjul-to-slf4j${slf4j.version}runtime

Add in logback.xml (logback-test.xml)
```
true`
```

Add in code

static {     SLF4JBridgeHandler.install(); }

回答4:

My solution :

SLF4JBridgeHandler.install(); java.util.logging.LogManager.getLogManager().getLogger("").setLevel( Level.INFO);

placing jul-to-slf4j on your app libs or glassfish libs, these redirect JUL to SLF4J (and thus in my case to LOG4J)

then for Jersey, you could do something like :

the last config is to avoid to be polluted by other loggers

回答5:

Solution that seems nice (considering the circumstances with the JUL bridging) and works for me, since I only have to write everything in the logback.groovy file.

(If you are not using logback.groovy configuration or logback at all, of course you have to put the logic part into some class (e.g. like class MyApp { static { /* log init code here */ } ... }).)

src/logback.groovy:

import org.slf4j.bridge.SLF4JBridgeHandler import ch.qos.logback.classic.jul.LevelChangePropagator  // for debug: just to see it in case something is logging/initialized before System.out.println( 'my myapp logback.groovy is loading' )  // see also: http://logback.qos.ch/manual/configuration.html#LevelChangePropagator // performance speedup for redirected JUL loggers def lcp = new LevelChangePropagator() lcp.context = context lcp.resetJUL = true context.addListener(lcp)  // needed only for the JUL bridge: http://stackoverflow.com/a/9117188/1915920 java.util.logging.LogManager.getLogManager().reset() SLF4JBridgeHandler.removeHandlersForRootLogger() SLF4JBridgeHandler.install() java.util.logging.Logger.getLogger( "global" ).setLevel( java.util.logging.Level.FINEST )  def logPattern = "%date |%.-1level| [%thread] %20.20logger{10}|  %msg%n"  appender("STDOUT", ConsoleAppender) {     encoder(PatternLayoutEncoder) {         pattern = logPattern     } }  /*// outcommenting in dev will not create dummy empty file appender("ROLLING", RollingFileAppender) {  // prod     encoder(PatternLayoutEncoder) {         Pattern = "%date %.-1level [%thread] %20.20logger{10}  %msg%n"     }     rollingPolicy(TimeBasedRollingPolicy) {         FileNamePattern = "${WEBAPP_DIR}/log/orgv-fst-gwt-%d{yyyy-MM-dd}.zip"     } } */  appender("FILE", FileAppender) {  // dev      // log to myapp/tmp (independent of running in dev/prod or junit mode:      //System.out.println( 'DEBUG: WEBAPP_DIR env prop:  "."='+new File('.').absolutePath+',  \${WEBAPP_DIR}=${WEBAPP_DIR},  env=' + System.getProperty( "WEBAPP_DIR" ))     String webappDirName = "war"     if ( new File( "./../"+webappDirName ).exists() )  // we are not running within a junit test         file = "../tmp/myapp.log"     else  // junit test         file = "tmp/myapp-junit-tests.log"      encoder(PatternLayoutEncoder) { pattern = logPattern } }  // without JUL bridge: //root(WARN, ["STDOUT", "ROLLING"])  // prod //root(DEBUG, ["STDOUT", "FILE"])  // dev  // with JUL bridge: (workaround: see links above) def rootLvl = WARN root(TRACE, [/*"STDOUT",*/ "FILE"]) // I manually added all "root package dirs" I know my libs are based on to apply // the root level to the second "package dir level" at least // depending on your libs used you could remove entries, but I would recommend // to add common entries instead (feel free to edit this post if you like to // enhance it anywhere) logger( "antlr", rootLvl ) logger( "de", rootLvl ) logger( "ch", rootLvl ) logger( "com", rootLvl ) logger( "java", rootLvl ) logger( "javassist", rootLvl ) logger( "javax", rootLvl ) logger( "junit", rootLvl ) logger( "groovy", rootLvl ) logger( "net", rootLvl ) logger( "org", rootLvl ) logger( "sun", rootLvl )   // my logger setup  logger( "myapp", DEBUG )   //logger( "org.hibernate.SQL", DEBUG )  // debug: log SQL statements in DEBUG mode //logger( "org.hibernate.type", TRACE )  // debug: log JDBC parameters in TRACE mode logger( "org.hibernate.type.BasicTypeRegistry", WARN )  // uninteresting  scan("30 seconds")  // reload/apply-on-change config every x sec

(recommended to be used by me since you can react with Java code vars/functions as you can see in here with, e.g. SLF4JBridgeHandler or the log dir regarding webappDirName)

(left the file complete since it gives a better impression how everything can be setup or as a staring template)

(may be relevant to somebody - my env: slf4j 1.7.5, logback 1.1.2, groovy 2.1.9)

转载请标明出处:JUL to SLF4J Bridge

文章来源: JUL to SLF4J Bridge

标签

slf4j

jul