[
https://issues.apache.org/jira/browse/LOG4J2-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465110#comment-17465110
]
Ralph Goers commented on LOG4J2-3288:
-------------------------------------
Carter, I haven't yet looked at the patch but Lookups are registered twice in
the Interpolator. The first is solely for use during configuration before the
PluginManager is available. Once it is the second initialization is performed
which causes all Lookup plugins to be registered.
I see no reason, why the event and structured data lookups would be needed
before the PluginManager is available. That may be true of bundle as well.
In short, I expect this issue and PR were unnecessary and should be reverted.
> 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)
