[
https://issues.apache.org/jira/browse/LOG4J2-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464872#comment-17464872
]
Ralph Goers commented on LOG4J2-3278:
-------------------------------------
Wow. I wasn't aware that ever worked with JsonTemplateLayout.
Yes, in 2.17.0 you will need to replace ${APP_NAME} with
${spring:spring.application.name} along with APP_VERSION and APP_ENV.
Recursion while processing log events has been disabled in 2.17.0 to address
CVE-2021-45105. However, we are considering whether we can safely re-enable
allowing a recursive call when the top level lookup is for a property such as
you are doing as that seems to be the primary negative impact of the change. We
will leave this issue open while we determine what can be done.
> 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)
