[
https://issues.apache.org/jira/browse/LOG4J2-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466929#comment-17466929
]
Ralph Goers edited comment on LOG4J2-3304 at 12/30/21, 4:16 PM:
----------------------------------------------------------------
I've looked at the PR but I don't understand how it has anything to do with
SpringEnvironmentHolder.getEnvironment() returning null.
What version of Spring Boot are you using? Spring Boot 2.6 has made changes
that we have not tested yet.
It might also be helpful to have a sample app that demonstrates the problem.
was (Author: [email protected]):
I've looked at the PR but I don't understand how it has anything to do with
SpringEnvironmentHolder.getEnvironment() returning null.
What version of Spring Boot are you using? Spring Boot 2.6 has made changes
that we have not tested yet.
> 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)
