You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@logging.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/07 00:35:00 UTC

[jira] [Commented] (LOG4J2-2105) ClassLoaderContextSelector should key based on log4j classes

    [ https://issues.apache.org/jira/browse/LOG4J2-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241247#comment-16241247 ] 

ASF GitHub Bot commented on LOG4J2-2105:
----------------------------------------

Github user cakofony commented on the issue:

    https://github.com/apache/logging-log4j2/pull/113
  
    updated


> 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)