[LOG4J2-3487] The LoggerConfig includeLocation defaults to true in 2.17.2

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.17.2
• Fix Version/s: 2.20.0
• Component/s: Configuration
• Assignee: Unassigned
• Reporter: Dave Messink
• Created: 24/Apr/22 19:14
• Updated: 02/Jan/23 06:30
• Resolved: 29/Dec/22 20:50

Description

We've found services running 2.17.2 to be slower than 2.17.1. A heat map indicates a StackWalker in log4j.

I found that the code that Logger plugin calls into has changed. In 2.17.1 the default config for includeLocation is based only on the configured value. In 2.17.2 it's based on the config value if present, but then defaults to !(context instanceof AsyncLoggerContext).

Since none of our Logger elements declare includeLocation - the default behavior has changed causing all LogEvents to include their location.

Issue Links

• is related to: LOG4J2-3491 High cpu, due to a change that cause to includeLocation by default for AsyncLogger