[
https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465111#comment-17465111
]
Carter Kozak commented on LOG4J2-3288:
--------------------------------------
There are several other places which use this path to create a new
StrSubstitutor (or subclass) outside of the configuration, I'm think we want
those to support the full breadth of lookup types.
I'm experimenting with a change to avoid the dual-world approach and load all
plugins we detect here, which seems to pass tests:
[https://github.com/apache/logging-log4j2/pull/656]
> 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)
