[
https://issues.apache.org/jira/browse/LOG4J2-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15478217#comment-15478217
]
Gary Gregory edited comment on LOG4J2-1209 at 9/9/16 8:56 PM:
--------------------------------------------------------------
Not as it is now. The arguments are passed along to any other APIs that can use
them like {{java.util.concurrent.ExecutorService.awaitTermination(long,
TimeUnit)}}.
My initial goal was to allow the caller of
{{Configurator.shutdown(LoggerContext, long, TimeUnit)}} to get Log4j to
shutdown completely and only return after all files are closed. As opposed to
returning "right away" while other threads might have files open writting,
closing, compressing and so on.
was (Author: garydgregory):
Not as it is now. The arguments are passed along to any other APIs that can use
them like {{java.util.concurrent.ExecutorService.awaitTermination(long,
TimeUnit)}}.
> 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]
