Geek asks and answers

Slf4j logback substituteLogger

I can no longer start my loggers using the gradle `jettyRuǹ task. The first problem with multiple bindings was not a problem. But now (after upgrading to gradle 1.4, I think) my loggers are not starting. The slf4j document talks about context reset software, but I would prefer to do it by configuration since jettyRun is used only for development.

$ gradle jettyRun
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jettyRun
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/opt/gradle-1.4/lib/logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bertrand/.gradle/caches/artifacts-23/filestore/ch.qos.logback/logback-classic/1.0.9/jar/258c3d8f956e7c8723f13fdea6b81e3d74201f68/logback-classic-1.0.9.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
SLF4J: The following loggers will not work because they were created
SLF4J: during the default configuration phase of the underlying logging system.
SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger
SLF4J: org.yajug.users.api.MembershipController
SLF4J: org.yajug.users.json.Serializer
SLF4J: org.yajug.users.api.MemberController
SLF4J: org.yajug.users.service.MemberServiceImpl
SLF4J: org.yajug.users.persistence.MongoConnector
+5
source share
1 answer

Finally, I found that not so:

  • The logging context is initialized lazily the first time the registrar is called.
  • In the context of my web application (a one-page web application that only performs asynchronous calls), the first page called 2 asynchronous requests
  • , , , , nop impl.
  • ,
+2

More articles:


All Articles