[
https://issues.apache.org/jira/browse/LOG4J2-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392564#comment-17392564
]
Carter Kozak commented on LOG4J2-3083:
--------------------------------------
[~mattsicker] I'm not sure those give us quite what I was looking for, the
location information is easier to verify because it's included in log events,
however the caller information we collect to select the correct context doesn't
appear to be verified there. Very possible that I've missed something though!
I think I've managed a reasonable test in this PR which also gives us logging
we can use to verify in production environments:
https://github.com/apache/logging-log4j2/pull/553 What do you think?
> Why the logger get by Slf4j LoggerFactory.getILoggerFactory() can only use
> current LoggerContext
> ------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-3083
> URL: https://issues.apache.org/jira/browse/LOG4J2-3083
> Project: Log4j 2
> Issue Type: Question
> Affects Versions: 2.13.3
> Environment: Spring Boot 2.4.5
> Slf4j
> Reporter: wanghao
> Assignee: Ralph Goers
> Priority: Major
> Labels: newbie
>
> In SpringBoot project with +test+ profile,
> org.slf4j.LoggerFactory.getLogger("xxx") can get test profile LoggerContext
> and read configuration from log4j2-test.xml.
> But
> org.slf4j.LoggerFactory.getILoggerFactory().getLogger("xxx") can only get
> current LoggerContext and read configuration from log4j2.xml.
>
> Is it designed like this? Why?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
