You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Mikael Ståldal (JIRA)" <ji...@apache.org> on 2016/09/05 13:29:20 UTC
[jira] [Updated] (LOG4J2-1549)
AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to
includeLocation=true
[ https://issues.apache.org/jira/browse/LOG4J2-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mikael Ståldal updated LOG4J2-1549:
-----------------------------------
Fix Version/s: 2.7
> AsyncLoggerContextSelector+PropertiesConfigurationBuilder defaults to includeLocation=true
> ------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1549
> URL: https://issues.apache.org/jira/browse/LOG4J2-1549
> Project: Log4j 2
> Issue Type: Bug
> Components: Configurators
> Reporter: Jason Bedard
> Assignee: Mikael Ståldal
> Fix For: 2.7
>
>
> The async documentation seems to indicate that includeLocation=false by default for [async loggers/appenders|https://logging.apache.org/log4j/2.x/manual/async.html#Location] and for the [all-async|https://logging.apache.org/log4j/2.x/manual/async.html#AllAsync]
> When using properties files PropertiesConfigurationBuilder seems to default to includeLocation=true for the [root logger|https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=blob;f=log4j-core/src/main/java/org/apache/logging/log4j/core/config/properties/PropertiesConfigurationBuilder.java;h=0f159ff3d33f638333e8ca530844d81437db99b5;hb=a493c04c046763140612307400f9189d8f0acd28#l299] and [loggers|https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=blob;f=log4j-core/src/main/java/org/apache/logging/log4j/core/config/properties/PropertiesConfigurationBuilder.java;h=0f159ff3d33f638333e8ca530844d81437db99b5;hb=a493c04c046763140612307400f9189d8f0acd28#l265], unless the logger/appender has type=asyncLogger/Appender or you manually specify includeLocation.
> I assume this is specific to properties config but haven't verified that.
> Currently using the latest log4j (2.6.2).
> Side note: I'm using my own ConfigurationFactory, but it just delegates to PropertiesConfigurationFactory which uses PropertiesConfigurationBuilder. I don't think this should effect anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org