[ https://issues.apache.org/jira/browse/LOG4J2-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519158#comment-17519158 ]
ASF subversion and git services commented on LOG4J2-3471: --------------------------------------------------------- Commit 5fc1e4957d9ba622d83bcf29c0aa3c54c34e19bf in logging-log4j2's branch refs/heads/release-2.x from Gary Gregory [ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=5fc1e4957d ] [LOG4J2-3471] log4j-1.2-api-2.17.2 throws exception while removing appender with name as null. Make internal use of the ConcurrentHashMap null safe. > log4j-1.2-api-2.17.2 throws exception while removing appender with name as > null > ------------------------------------------------------------------------------- > > Key: LOG4J2-3471 > URL: https://issues.apache.org/jira/browse/LOG4J2-3471 > Project: Log4j 2 > Issue Type: Bug > Affects Versions: 2.17.2 > Reporter: Rajesh > Assignee: Gary D. Gregory > Priority: Major > > The log4j 1.2 bridge for 2.17.2 throws null pointer exception while removing > Null appender > viz. org.apache.log4j.varia.NullAppender > The class AppenderAttachableImpl adds the null appender to the > concurrenthashmap as "null" and on removal there is no check for null and > removes the nullappender with name null hence the NullPointerexception. > Caused by: java.lang.NullPointerException > at java.util.concurrent.ConcurrentHashMap.remove(Unknown Source) > at > org.apache.log4j.helpers.AppenderAttachableImpl.removeAppender(AppenderAttachableImpl.java:93) > at org.apache.log4j.Category.removeAppender(Category.java:618) -- This message was sent by Atlassian Jira (v8.20.1#820001)