[logback-user] jul-to-slf4j conflicts with logback-classic

cowwoc cowwoc at bbs.darktech.org
Thu Oct 23 01:19:30 CEST 2008


I need your help with this.

I noticed that I can deploy the libraries just fine so long as I omit the
call to SLF4JBridgeHandler.install(). If I invoke that method then:

1) I never see any more output from stdout
2) Glassfish no longer replies to commands (I have to kill it using task

It also doesn't look like logback.xml is getting picked up because I have
debug="true" in my configuration but I see nothing special on startup.

Can we schedule another IRC session to troubleshoot this?


cowwoc wrote:
> Hi,
> If I deploy:
> slf4j-api
> logback-classic
> logback-core
> jul-to-slf4j
> I get:
> Deploying application in domain failed; Logging factory implementation
> cannot be null. See also http://www.slf4j.org/codes.html#null_LF
> but if I remove jul-to-slf4j from the classpath it works just fine
> (except, obviously, jul-to-slf4j is disabled).
> I am invoking SLF4JBridgeHandler.install() from within a
> ServletContextListener. Perhaps this is too late somehow?
> What am I doing wrong?
> Thank you,
> Gili

View this message in context: http://www.nabble.com/jul-to-slf4j-conflicts-with-logback-classic-tp19590922p20121591.html
Sent from the Logback User mailing list archive at Nabble.com.

More information about the Logback-user mailing list