[ https://issues.apache.org/jira/browse/LOG4J2-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718183#comment-14718183 ]
Mikael Ståldal commented on LOG4J2-1108: ---------------------------------------- According to [http://docs.oracle.com/javase/7/docs/api/java/util/logging/Logger.html], it is only in {{setLevel()}} you are allowed to pass null as Level, so we don't have to support null Level to the other methods in Logger (such as log(Level, ...)). So I suggest we put the fix in {{CoreLogger.setLevel()}} and don't change {{DefaultLevelConverter}}. > NullPointerException when passing null to java.util.logging.Logger.setLevel() > ----------------------------------------------------------------------------- > > Key: LOG4J2-1108 > URL: https://issues.apache.org/jira/browse/LOG4J2-1108 > Project: Log4j 2 > Issue Type: Bug > Components: JUL adapter > Affects Versions: 2.4 > Environment: > -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager > Reporter: Mikael Ståldal > Priority: Blocker > > When using a 3rd party library (Twitter Finagle) which uses a custom > java.util.logging.Level, I get this: > {code} > Exception in thread "main" java.lang.NullPointerException > at > java.util.concurrent.ConcurrentHashMap.hash(ConcurrentHashMap.java:333) > at > java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:988) > at > org.apache.logging.log4j.jul.DefaultLevelConverter.toLevel(DefaultLevelConverter.java:119) > at > org.apache.logging.log4j.jul.LevelTranslator.toLevel(LevelTranslator.java:72) > at > org.apache.logging.log4j.jul.CoreLogger.setLevel(CoreLogger.java:47) > at com.twitter.logging.Logger.setLevel(Logger.scala:63) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org