[
https://issues.apache.org/jira/browse/LOG4J2-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16061959#comment-16061959
]
ASF subversion and git services commented on LOG4J2-1801:
---------------------------------------------------------
Commit ab33665bf3eb542ef0dc751f9b44a59043003fb0 in logging-log4j2's branch
refs/heads/master from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ab33665 ]
LOG4J2-1801 Add more detail to WARN "Ignoring log event" messages printed to
the console after log4j was shut down.
> 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.4.14#64029)
