You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2018/02/26 22:27:00 UTC

[jira] [Commented] (LOG4J2-2272) includeLocation property for async loggers

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

Remko Popma commented on LOG4J2-2272:
-------------------------------------

Where in the code is  {{includeLocation}} defaulted to true? Is this what you see when stepping through the code in a debugger or when reading the code?

> includeLocation property for async loggers
> ------------------------------------------
>
>                 Key: LOG4J2-2272
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2272
>             Project: Log4j 2
>          Issue Type: Question
>          Components: Core
>    Affects Versions: 2.10.0
>            Reporter: Anton Korenkov
>            Priority: Minor
>
> According to [link|https://logging.apache.org/log4j/2.0/manual/async.html]:
> {quote}By default, [location|https://logging.apache.org/log4j/2.0/manual/async.html#Location] is not passed to the I/O thread by asynchronous loggers. If one of your layouts or custom filters needs location information, you need to set "includeLocation=true" in the configuration of all relevant loggers, including the root logger.
> {quote}
> However, if I create logger with default configuration and '-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector' vm option 'includeLocation' defaults to 'true'. Is it expected behavior or glitch?



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