[LOG4J2-2791] Timestamp handling ordering regression in JsonLayout between 2.10.0 and 2.11.0

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.13.2
• Assignee: Unassigned
• Reporter: Johan Karlberg
• Created: 26/Feb/20 10:07
• Updated: 11/Jun/20 10:54
• Resolved: 12/Apr/20 17:41

Description

The introduction of the instant timestamp caused a regression in the ordeirng of the timestamp as follows:

2.10.0:
{
  "timeMillis" : 1582633940829,
  "thread" : "main",
  "level" : "INFO",
  "loggerName" : "example",
  "message" : "Example log-entry",
  "endOfBatch" : false,
  "loggerFqcn" : "org.apache.logging.log4j.spi.AbstractLogger",
  "threadId" : 1,
  "threadPriority" : 5
}

2.11.0:
{
  "thread" : "main",
  "level" : "INFO",
  "loggerName" : "example",
  "message" : "Example log-entry",
  "endOfBatch" : false,
  "loggerFqcn" : "org.apache.logging.log4j.spi.AbstractLogger",
  "instant" : {
    "epochSecond" : 1582634065,
    "nanoOfSecond" : 603815000
  },
  "threadId" : 1,
  "threadPriority" : 5
}

3.0.0-SNAPSHOT (and expected behaviour):
{
  "instant" : {
    "epochSecond" : 1582711040,
    "nanoOfSecond" : 521000000
  },
  "thread" : "main",
  "level" : "INFO",
  "loggerName" : "example",
  "message" : "Example log-entry",
  "endOfBatch" : false,
  "loggerFqcn" : "org.apache.logging.log4j.spi.AbstractLogger",
  "threadId" : 1,
  "threadPriority" : 5
}

As can be seen, the instant field does not sort near the start of the event, as the code appears to intend (and how it works on master). This causes issues for us in log aggregation where large events do not look unique (due to large messages, which sort before the instant)

The problem is in LogEventJsonMixIn.java where an XML constant is used of EL_INSTANT instead of the Json constant, where the constant differs in case, which is relevant to the jackson serializer, leaving "instant" unsorted, and "Instant" not found.

Issue Links

• links to: GitHub Pull Request #345