You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Mck SembWever (JIRA)" <ji...@apache.org> on 2014/05/16 12:44:20 UTC
[jira] [Created] (LOG4J2-639) NPE in AsyncLogger.log(..)
Mck SembWever created LOG4J2-639:
------------------------------------
Summary: NPE in AsyncLogger.log(..)
Key: LOG4J2-639
URL: https://issues.apache.org/jira/browse/LOG4J2-639
Project: Log4j 2
Issue Type: Bug
Components: Appenders
Affects Versions: 2.0-rc1
Reporter: Mck SembWever
Our production environment suffers from
{noformat}
java.lang.NullPointerException at org.apache.logging.log4j.core.async.AsyncLogger.log(AsyncLogger.java:273) at org.apache.logging.log4j.spi.AbstractLoggerWrapper.log(AbstractLoggerWrapper.java:121) at org.apache.logging.log4j.spi.AbstractLogger.info(AbstractLogger.java:1006) at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:873) at org.springframework.context.support.AbstractApplicationContext$1.run(AbstractApplicationContext.java:809)
{noformat}
It looks like something in our app is still logging despite the AsyncLogger having been stopped (and the disruptor field set to null).
The logger could print out a more informative message in this situation.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org