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 "Remko Popma (JIRA)" <ji...@apache.org> on 2017/01/10 15:06:58 UTC
[jira] [Resolved] (LOG4J2-1779) AsyncLogger does not lookup
properties
[ https://issues.apache.org/jira/browse/LOG4J2-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma resolved LOG4J2-1779.
---------------------------------
Resolution: Fixed
Fixed in commit a686a4e.
> AsyncLogger does not lookup properties
> --------------------------------------
>
> Key: LOG4J2-1779
> URL: https://issues.apache.org/jira/browse/LOG4J2-1779
> Project: Log4j 2
> Issue Type: Bug
> Components: Core, Lookups
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.8
>
>
> When copying configuration Properties into the context data map of each log event, property values that start with "${" should be treated as a Lookup and be resolved with {{StrSubstitutor.replace}}.
> AsyncLogger has a bug such that this lookup does not happen and the original value (starting with "${") is put in the contxt data map of the log event.
--
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