[
https://issues.apache.org/jira/browse/LOG4J2-2320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16441430#comment-16441430
]
Matt Sicker commented on LOG4J2-2320:
-------------------------------------
There are still many places in the log4j codebase that don't use parameterized
logging. Except for some specific scenarios that involve passing around a
StringBuilder between several classes (see how plugin factories are debugged
for example), you can usually just use parameterized logging. The old string
concatenated logs can be updated to parameterized logging (it's just tedious).
> AbstractLogger NPE hides actual cause when getFormat returns null
> -----------------------------------------------------------------
>
> Key: LOG4J2-2320
> URL: https://issues.apache.org/jira/browse/LOG4J2-2320
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.11.0
> Reporter: Carter Kozak
> Assignee: Carter Kozak
> Priority: Major
> Fix For: 3.0.0
>
>
> NPE on Message.getFormat().length()
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.logging.log4j.spi.AbstractLogger.handleLogMessageException(AbstractLogger.java:2184)
> ~[log4j-api-2.11.0.jar:2.11.0]
> at
> org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2173)
> ~[log4j-api-2.11.0.jar:2.11.0]
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2125)
> ~[log4j-api-2.11.0.jar:2.11.0]
> at
> org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2108)
> ~[log4j-api-2.11.0.jar:2.11.0]
> at
> org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1827)
> ~[log4j-api-2.11.0.jar:2.11.0]
> at
> org.apache.logging.log4j.spi.AbstractLogger.trace(AbstractLogger.java:2272)
> ~[log4j-api-2.11.0.jar:2.11.0]{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
