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

ASF subversion and git services commented on LOG4J2-2322:
---------------------------------------------------------

Commit 58232a1623dd050c0d31f244395b15b385283d1f in logging-log4j2's branch 
refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=58232a1 ]

[LOG4J2-2322] Custom async ContextSelectors disable location by default

AsyncLoggerContextSelector disables "includeLocation" on loggers
unless specified. Custom ContextSelector implementations will
trigger this logic as well.


> Custom Async ContextSelectors should disable location by default
> ----------------------------------------------------------------
>
>                 Key: LOG4J2-2322
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2322
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>            Reporter: Carter Kozak
>            Assignee: Carter Kozak
>            Priority: Major
>
> When AsyncLoggerContextSelector is selected, we modify the default value of 
> LoggerConfig.includeLocation from true to false.
> Custom asynchronous ContextSelector implementations should also trigger this 
> logic to avoid unnecessarily work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to