[
https://issues.apache.org/jira/browse/LOG4J2-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15816238#comment-15816238
]
Gary Gregory commented on LOG4J2-1780:
--------------------------------------
What I think we need to consider here is if reconfiguring a {{LoggerContext}}
means that we should:
- stop it
- reconfigure it
- start it
The {{org.apache.logging.log4j.core.LoggerContext.stop(long, TimeUnit)}} method
stops all executors.
Right now, reconfiguring does not do that.
Callers of {{setConfiguration}} like the {{reconfigure}} methods could stop (if
needed) and start itself.
Needs more thought...
> LoggerContext does not shut down old executor services when creating new ones
> during reconfiguration
> ----------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1780
> URL: https://issues.apache.org/jira/browse/LOG4J2-1780
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.7
> Reporter: Mikael Ståldal
>
> LoggerContext does not shut down old executor services when creating new ones
> during reconfiguration in {{LoggerContext.setConfiguration}}.
--
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
