[
https://issues.apache.org/jira/browse/LOG4J2-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17495265#comment-17495265
]
ASF subversion and git services commented on LOG4J2-3304:
---------------------------------------------------------
Commit 8e89ecd4a94e2f600423564c8381f8a0f9b12fe6 in logging-log4j2's branch
refs/heads/dependabot/maven/org.apache.felix-maven-bundle-plugin-5.1.4 from
Francis
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=8e89ecd ]
LOG4J2-3304 - Fix issue that the initialize status of LogManager is not set
when factoryClassName is present and instantiate successfully (#676)
> SpringEnvironmentHolder getEnvironment always return null
> ---------------------------------------------------------
>
> Key: LOG4J2-3304
> URL: https://issues.apache.org/jira/browse/LOG4J2-3304
> Project: Log4j 2
> Issue Type: Bug
> Components: API, Spring
> Affects Versions: 2.17.1
> Reporter: francis
> Priority: Major
>
> I am using SpringLookup and SpringProfileArbiter for conditional
> configuration, but it doesn't work. I debugged into SpringEnvironmentHolder
> and found that the getEnvironment method always returns null. Then I found
> the root cause is that when the factoryClassName is present and load
> successfully, the LogManagerStatus is not set in the static block of
> LogManager. It could be a bug, please take a look
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
