Remko Popma created LOG4J2-1801:
-----------------------------------
Summary: Add more detail to WARN Ignoring log event after log4j
was shut down
Key: LOG4J2-1801
URL: https://issues.apache.org/jira/browse/LOG4J2-1801
Project: Log4j 2
Issue Type: Improvement
Components: Core
Affects Versions: 2.8
Reporter: Remko Popma
Assignee: Remko Popma
Currently, AsyncLoggerConfigDisruptor::enqueueEvent,
AsyncLoggerDisruptor::tryPublish and
AsyncLoggerDisruptor::enqueueLogMessageInfo catch exceptions when logging
occurs after the context has been stopped.
These errors are currently handled by logging to the status logger:
{code}
LOGGER.warn("Ignoring log event after log4j was shut down.", contextName);
{code}
This can be improved by adding more details from the LogEvent that is being
dropped:
{code}
LOGGER.warn("Ignoring log event after log4j was shut down: {} [{}] {}",
event.getLevel(),
event.getLoggerName(), event.getMessage().getFormattedMessage()
+ (event.getThrown() == null ? "" :
Throwables.toStringList(event.getThrown())));
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
