karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5116) Defining karaf.log.console as a log4j2 log level causes exceptions
Date Tue, 04 Jul 2017 11:15:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073491#comment-16073491
] 

ASF subversion and git services commented on KARAF-5116:
--------------------------------------------------------

Commit 2a564c9a062a46460aed030efba8abe61cc28f9d in karaf's branch refs/heads/karaf-4.0.x from
[~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=2a564c9 ]

Revert "[KARAF-5116] Updating documentation related to karaf.log.console property"

This reverts commit 816df200a7b9700f034e2c59325a5d3d009b0eda.


> 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
>
>
> 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.<init>(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.<init>(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)

Mime
View raw message