Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8FCFB200CC6 for ; Tue, 4 Jul 2017 08:00:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8E8B3160BF9; Tue, 4 Jul 2017 06:00:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D547E160BEC for ; Tue, 4 Jul 2017 08:00:05 +0200 (CEST) Received: (qmail 40763 invoked by uid 500); 4 Jul 2017 06:00:05 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 40751 invoked by uid 99); 4 Jul 2017 06:00:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Jul 2017 06:00:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 714FAD02C3 for ; Tue, 4 Jul 2017 06:00:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id bVqyX_V7gk3Z for ; Tue, 4 Jul 2017 06:00:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AC93F5FB7F for ; Tue, 4 Jul 2017 06:00:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 40D7FE0D48 for ; Tue, 4 Jul 2017 06:00:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id A5B692460C for ; Tue, 4 Jul 2017 06:00:01 +0000 (UTC) Date: Tue, 4 Jul 2017 06:00:01 +0000 (UTC) From: "Grzegorz Grzybek (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KARAF-5116) Defining karaf.log.console as a log4j2 log level causes exceptions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Jul 2017 06:00:06 -0000 [ https://issues.apache.org/jira/browse/KARAF-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated KARAF-5116: ------------------------------------ Fix Version/s: 4.0.10 4.1.2 4.2.0 > Defining karaf.log.console as a log4j2 log level causes exceptions > ------------------------------------------------------------------ > > Key: KARAF-5116 > URL: https://issues.apache.org/jira/browse/KARAF-5116 > Project: Karaf > Issue Type: Bug > Affects Versions: 4.1.1 > Reporter: Jamie Kemp > Assignee: Grzegorz Grzybek > Priority: Minor > Fix For: 4.2.0, 4.1.2, 4.0.10 > > > Running karaf 4.1.1, defining karaf.log.console as DEBUG to switch on the console appender (to get to logging when running under pax-exam) results in the following exceptions: > {code} > java.lang.IllegalArgumentException: Bad level "DEBUG" > at java.util.logging.Level.parse(Level.java:482) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:109) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70) > at org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75) > at org.apache.karaf.main.Main.launch(Main.java:244) > at org.apache.karaf.main.Main.main(Main.java:178) > java.lang.IllegalArgumentException: Bad level "DEBUG" > at java.util.logging.Level.parse(Level.java:482) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:109) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70) > at org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75) > at org.apache.karaf.main.KarafActivatorManager.(KarafActivatorManager.java:49) > at org.apache.karaf.main.Main.launch(Main.java:280) > at org.apache.karaf.main.Main.main(Main.java:178) > java.lang.IllegalArgumentException: Bad level "DEBUG" > at java.util.logging.Level.parse(Level.java:482) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlersInternal(BootstrapLogManager.java:109) > at org.apache.karaf.main.util.BootstrapLogManager.getDefaultHandlers(BootstrapLogManager.java:70) > at org.apache.karaf.main.util.BootstrapLogManager.configureLogger(BootstrapLogManager.java:75) > at org.apache.karaf.main.lock.SimpleFileLock.(SimpleFileLock.java:40) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:422) > at org.apache.karaf.main.Main.createLock(Main.java:476) > at org.apache.karaf.main.Main.doMonitor(Main.java:378) > at org.apache.karaf.main.Main.access$100(Main.java:75) > at org.apache.karaf.main.Main$3.run(Main.java:369) > {code} > Looks like BootstrapLogManager attempts to use java.util.logging levels which DEBUG is not one of them. This however does result in valid logging out via log4j2 to the console appender. > Using a valid java.util.logger level (tried FINE during testing) results in logging to the console from 'SimpleFileLock' but nothing from log4j2. -- This message was sent by Atlassian JIRA (v6.4.14#64029)