Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE5FB107FD for ; Fri, 28 Aug 2015 05:51:45 +0000 (UTC) Received: (qmail 57698 invoked by uid 500); 28 Aug 2015 05:51:45 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 57648 invoked by uid 500); 28 Aug 2015 05:51:45 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 57635 invoked by uid 99); 28 Aug 2015 05:51:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2015 05:51:45 +0000 Date: Fri, 28 Aug 2015 05:51:45 +0000 (UTC) From: "Gary Gregory (JIRA)" To: log4j-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (LOG4J2-1108) NullPointerException when using custom java.util.logging.Level MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4J2-1108?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D147= 18091#comment-14718091 ]=20 Gary Gregory edited comment on LOG4J2-1108 at 8/28/15 5:51 AM: --------------------------------------------------------------- It also looks like our setLevel(Level) implementation {{org.apache.logging.= log4j.jul.CoreLogger.setLevel(Level)}} does not perform the proper security= check: {quote} Throws: SecurityException - if a security manager exists and if the caller does not= have LoggingPermission("control"). {quote} Am I reading that right? If so. then that should be covered by a new issue. was (Author: garydgregory): It also looks like our setLevel(Level) implementation {{org.apache.logging.= log4j.jul.CoreLogger.setLevel(Level)}} does not perform the proper security= check: {quote} Throws: SecurityException - if a security manager exists and if the caller does not= have LoggingPermission("control"). {quote} Am I reading that right? That would be covered by a new issue. > NullPointerException when using custom java.util.logging.Level > -------------------------------------------------------------- > > 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=3Dorg.apache.logging.log= 4j.jul.LogManager > Reporter: Mikael St=C3=A5ldal > > 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.j= ava:988) > at org.apache.logging.log4j.jul.DefaultLevelConverter.toLevel(Def= aultLevelConverter.java:119) > at org.apache.logging.log4j.jul.LevelTranslator.toLevel(LevelTran= slator.java:72) > at org.apache.logging.log4j.jul.CoreLogger.setLevel(CoreLogger.ja= va: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-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org