[
https://issues.apache.org/jira/browse/LOG4J2-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723547#comment-14723547
]
Gary Gregory commented on LOG4J2-1108:
--------------------------------------
It is functional now but [~ralphgoers] said he want to look at a more efficient
implementation.
> 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
> Assignee: Gary Gregory
> Priority: Blocker
> Fix For: 2.4
>
> Attachments: setlevel.patch
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
