[
https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465857#comment-17465857
]
ASF subversion and git services commented on LOG4J2-3288:
---------------------------------------------------------
Commit 14f0bd06e64a1dd2c13b7deda7380fe9a2b7c755 in logging-log4j2's branch
refs/heads/release-2.x from Carter Kozak
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=14f0bd0 ]
Revert "LOG4J2-3288 Interpolator non-plugin ctor includes all core lookups"
This reverts commit 68fdfcec221ec9458ee0fd83d97d95977c4b54b7.
> Interpolator non-plugin codepath doesn't include all log4j-core lookups
> -----------------------------------------------------------------------
>
> Key: LOG4J2-3288
> URL: https://issues.apache.org/jira/browse/LOG4J2-3288
> Project: Log4j 2
> Issue Type: Bug
> Components: Configuration, Core
> Affects Versions: 2.17.0
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 2.17.1
>
>
> It appears that {{bundle}} {{{}event{}}}, and {{sd}} lookups are not
> registered.
> There's a comment suggesting that the PluginManager could be used, however
> that will require additional validation before I'm comfortable enabling it:
> Logging initialization is very static and tricky, and it's easy to produce
> deadlocks when referencing logging code within initialization.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
