[LOG4J2-2863] LocationAwareLogger implementation fails to extract throwable from message

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.13.3
• Component/s: SLF4J Bridge
• Assignee: Unassigned
• Reporter: Nicolas Pepin-Perreault
• Created: 07/Jun/20 15:02
• Updated: 07/Sep/22 18:31
• Resolved: 07/Sep/22 18:31

Description

(Note: I looked but didn't see any issues for this - though I had a hard time coming up with a quick summary, so maybe I didn't search for the right things, sorry in advance if this is a duplicate)

 

When using the SLF4J bridge's Log4JLogger class as a LocationAwareLogger, if no throwable is given but the ParametrizedMessage contains one, it seems it is not properly extracted.

 

One thing I saw, is at org.apache.logging.slf4j.Log4JLogger:372, it seems there's a check if we're already passing a throwable, and we only pick up the one from the message if we already are. Is this intentional, and if so, what's the reasoning? From looking at ParametrizedMessage, it seems the throwable is picked up from the message arguments iff there was no throwable initially given, but maybe I misunderstood this.

 

The use case here is that we have a delegating logger class, but we want the location to be properly computed, so we need to access the logger as a LocationAwareLogger.

 

Cheers,

Issue Links

• is duplicated by: LOG4J2-3585 Exception in Parameterized Message not logged using LocationAwareLogger API