[
https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465052#comment-17465052
]
Carter Kozak edited comment on LOG4J2-3278 at 12/24/21, 4:34 PM:
-----------------------------------------------------------------
I think this may actually be the same issue as
https://issues.apache.org/jira/browse/LOG4J2-3204
The spring lookup package name was listed incorrectly, [~zhichun.zhang] can you
verify using the latest snapshot build?
(tagging [~vy] who may be interested in following)
was (Author: ckozak):
I think this may actually be the same issue as
https://issues.apache.org/jira/browse/LOG4J2-3204
The spring lookup package name was listed incorrectly, [~zhichun.zhang] can you
verify using the latest snapshot release?
(tagging [~vy] who may be interested in following)
> SpringLookup log4j2 2.17.0 version Invalidation
> ------------------------------------------------
>
> Key: LOG4J2-3278
> URL: https://issues.apache.org/jira/browse/LOG4J2-3278
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.17.0
> Reporter: ZhangZhichun
> Priority: Major
> Attachments: JHJsonEventLayoutV1.json,
> image-2021-12-23-14-20-54-699.png, image-2021-12-23-14-22-17-392.png,
> image-2021-12-23-15-04-36-171.png, log-spring.xml
>
>
> SpringLookup 2.16.0 is ok,Invalid after update to 2.17.0.
> ${spring:spring.application.name} in log could not be resolved.
> my springboot version 2.4.12
> !image-2021-12-23-14-20-54-699.png!
> !image-2021-12-23-15-04-36-171.png!
> show log result:
> !image-2021-12-23-14-22-17-392.png!
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
