[
https://issues.apache.org/jira/browse/LOG4J2-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-1084.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.4
Phillip,
Thank you for your report and patch.
A fix is now is Git master.
Please verify and close this ticket.
Gary
> Misleading StatusLogger WARN event in LogManager with java.util.Map
> -------------------------------------------------------------------
>
> Key: LOG4J2-1084
> URL: https://issues.apache.org/jira/browse/LOG4J2-1084
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.3
> Reporter: Philipp Schneider
> Priority: Minor
> Labels: easyfix
> Fix For: 2.4
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> In the class org.apache.logging.log4j.LogManager in the API package there is
> a logical problem with finding the factory.
> In the static initialization block starting at line 70 you try to create a
> factory instance from the factory class specified in the property
> "log4j2.loggerContextFactory". If that fails you try to find the class in all
> the supplied providers.
> The problem comes in line 104. You check whether the list of factories is
> empty and if it is not you automatically assume that there is more than 1
> provider which has that class.
> Because of this I get the following logging entries on each startup:
> WARN StatusLogger Multiple logging implementations found:
> Factory: org.apache.logging.log4j.core.impl.Log4jContextFactory, Weighting: 10
> Using factory: org.apache.logging.log4j.core.impl.Log4jContextFactory
> As you can see, it clearly outputs only a single possible factory and also
> uses that one.
> Hope to see this fixed in 2.4 since it is really a minor issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
