[
https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035822#comment-15035822
]
Ralph Goers commented on LOG4J2-1209:
-------------------------------------
If they hang that is a very serious problem. Attempts to log to a non-started
LoggerContext is doomed. Attempts to log to a non-started Appender is going to
fail. There should be no reason LoggerContext.start() hangs so I would make
sure whatever it does adheres to that. A non-started Appender, while serious,
will cause a logging event to fail and can be dealt with if a FailoverAppender
is configured.
> LoggerContext.stop() hangs indefinitely if any Appender's stop() method hangs
> -----------------------------------------------------------------------------
>
> Key: LOG4J2-1209
> URL: https://issues.apache.org/jira/browse/LOG4J2-1209
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.4.1
> Reporter: Mikael Ståldal
>
> {{LoggerContext.stop()}} hangs indefinitely if any Appender's {{stop()}}
> method hangs.
> It is not possible to protect from this by wrapping a problematic Appender in
> AsyncAppender since {{LoggerContext.stop()}} will stop all appenders no
> matter how they are used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
