[
https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480303#comment-17480303
]
Carter Kozak commented on LOG4J2-3288:
--------------------------------------
[~rgoers] I'd like to reintroduce the reverted behavior based on
https://issues.apache.org/jira/browse/LOG4J2-3358 where the initial non-plugin
interpolator is still used throughout the configuration since it isn't created
based on nodes. There are several other places where new instances are created,
in which we'd expect them to support the full breadth of features.
PR is https://github.com/apache/logging-log4j2/pull/726
> 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
>
> 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)
