[
https://issues.apache.org/jira/browse/LOG4J2-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sunshaowei updated LOG4J2-3005:
-------------------------------
Description: the input string is \{"id":"123","name":{}}，if the value of
name is empty，the called API
org.apache.logging.log4j.core.config.LoggerConfig#log(java.lang.String,
java.lang.String, org.apache.logging.log4j.Marker,
org.apache.logging.log4j.Level, org.apache.logging.log4j.message.Message,
java.lang.Throwable) will transfer the message to \{"id":"123","name":{id=123,
name={}}}。so when after we called the API
org.slf4j.spi.LocationAwareLogger#log，the output log is not the same as the
input we expected. (was:
输入的格式格式为\{"id":"123","name":{}}的字符串，如果{}中的内容为空，则会在方法org.apache.logging.log4j.core.config.LoggerConfig#log(java.lang.String,
java.lang.String, org.apache.logging.log4j.Marker,
org.apache.logging.log4j.Level, org.apache.logging.log4j.message.Message,
java.lang.Throwable)中被填充为 \{"id":"123","name":{id=123,
name={}}}。导致调用org.slf4j.spi.LocationAwareLogger#log接口后，打印的日志的结果与原始的结果不一致)
Summary: log4j cannot correctly parse the input Message which contains
{} (was: log4j无法正确解析带{}的日志报文)
> log4j cannot correctly parse the input Message which contains {}
> ----------------------------------------------------------------
>
> Key: LOG4J2-3005
> URL: https://issues.apache.org/jira/browse/LOG4J2-3005
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.13.2
> Reporter: sunshaowei
> Priority: Major
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> the input string is \{"id":"123","name":{}}，if the value of name is empty，the
> called API
> org.apache.logging.log4j.core.config.LoggerConfig#log(java.lang.String,
> java.lang.String, org.apache.logging.log4j.Marker,
> org.apache.logging.log4j.Level, org.apache.logging.log4j.message.Message,
> java.lang.Throwable) will transfer the message to
> \{"id":"123","name":{id=123, name={}}}。so when after we called the API
> org.slf4j.spi.LocationAwareLogger#log，the output log is not the same as the
> input we expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
