[LOG4J2-2734] Backwards incompatible change of JsonLayout from 2.11 to 2.12

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.12.0, 2.12.1
• Fix Version/s: 2.13.1
• Component/s: Core
• Assignee: Unassigned
• Reporter: Guilherme Trein
• Created: 09/Dec/19 18:38
• Updated: 23/Feb/20 07:10
• Resolved: 23/Feb/20 07:10

Description

I'm reporting what I believe is a regression. After updating from v2.11.2 to v2.12.1, I noticed that the JSON log entries changed for my application:

 

Here is what I had in v2.11.2:

{
  "thread":"main",
  "level":"INFO",
  "loggerName":"com.some.Class",
  "message":"Attempting to report profile data: lastAttempted=1575645588542; now=1575647388708;",
  "endOfBatch":true,
  "loggerFqcn":"org.apache.logging.slf4j.Log4jLogger",
  "instant":{"epochSecond":1575907354,"nanoOfSecond":460000000},
  "threadId":1,
  "threadPriority":5,
  "timestamp":"2019-12-06T15:49:48.708Z"
}

Here is what I got in v2.12.1:

{
  "logEvent": "Attempting to report profile data: lastAttempted=1575645588542; now=1575647388708;",
  "timestamp": "2019-12-06T15:49:48.708Z"
}

I believe the offending commit is this. For some reason, the implementation of AbstractJacksonLayout#toSerializable(LogEvent, Writer) changed (the method call to convertMutableToLog4jEvent was deleted).

Issue Links

• duplicates: LOG4J2-2652 JSON output wrong when using additonal fields