[logback-dev] [JIRA] Updated: (LBCLASSIC-74) NullPointerException in Logger after container restart

Manel Clos (JIRA) noreply-jira at qos.ch
Fri Oct 3 12:53:50 CEST 2008

     [ http://jira.qos.ch/browse/LBCLASSIC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manel Clos updated LBCLASSIC-74:

    Attachment: minimalwebapp.zip

Testcase showing the problem.

maven webapp archetype, index.jsp calling the testcase.

Run the webapp, see the "Hello World" message. Restart Tomcat and try to access the webapp again. A NPE should happen.

My *real* application started failing after migration from log4j to logback. This testcase is just a simplification.

> NullPointerException in Logger after container restart
> ------------------------------------------------------
>                 Key: LBCLASSIC-74
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-74
>             Project: logback-classic
>          Issue Type: Bug
>    Affects Versions: 0.9.9
>         Environment: Eclipse 3.4, Java 5, Tomcat 5.5.26, plain JSP (no servlet)
>            Reporter: Manel Clos
>            Assignee: Logback dev list
>         Attachments: minimalwebapp.zip
> Hi,
> loggerContext in the Logger class is null after container restart. This will produce a NPE when trying to further use logback.
> java.lang.NullPointerException
> 	at ch.qos.logback.classic.Logger.callTurboFilters(Logger.java:775)
> 	at ch.qos.logback.classic.Logger.isDebugEnabled(Logger.java:630)
> 	at ch.qos.logback.classic.Logger.isDebugEnabled(Logger.java:613)
> 	at test.LogbackTest.testLogger(LogbackTest.java:15)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list