[
https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033861#comment-15033861
]
Mikael Ståldal edited comment on LOG4J2-1209 at 12/1/15 3:27 PM:
-----------------------------------------------------------------
Or else we need to review all appenders in {{log4j-core}} and make sure that
none of them can hang indefinitely on {{stop()}}, perhaps adding
{{shutdownTimeout}} parameter to some of them (like {{AsyncAppender}} already
have).
And update documentation to alert 3rd party appender developers to do the same.
was (Author: mikaelstaldal):
Or else we need to review all appenders in {{log4j-core}} and make sure that
none of them can hang indefinitely on {{stop()}}, perhaps adding
{{shutdownTimeout}} parameter to some of them (like {{AsyncAppender}} already
have).
> 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.
> We have some Appenders which can hang indefinitely, see
> [https://issues.apache.org/jira/browse/LOG4J2-1191].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
