[
https://issues.apache.org/jira/browse/LOG4J2-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247636#comment-16247636
]
ASF GitHub Bot commented on LOG4J2-2105:
----------------------------------------
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/113
After reading the docs
[here](https://logging.apache.org/log4j/2.x/manual/appenders.html#FileAppender)
I think this change would break things. Closing.
> ClassLoaderContextSelector should key based on log4j classes
> ------------------------------------------------------------
>
> Key: LOG4J2-2105
> URL: https://issues.apache.org/jira/browse/LOG4J2-2105
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Reporter: Carter Douglas Kozak
>
> ClassLoaderContextSelector should create context map keys based on the
> instances of log4j-core classes, not necessarily the classloader. When log4j
> is initialized as shared beween sub loaders, sharing a single context is
> preferrable.
> AsyncLoggerContextSelector defautlt context name shouldn't depend on the
> current thread name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
