You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2018/12/04 05:01:00 UTC
[jira] [Assigned] (KARAF-6027) `log:get` does not report the right
log level for loggers that contain numbers
[ https://issues.apache.org/jira/browse/KARAF-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-6027:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> `log:get` does not report the right log level for loggers that contain numbers
> ------------------------------------------------------------------------------
>
> Key: KARAF-6027
> URL: https://issues.apache.org/jira/browse/KARAF-6027
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.1
> Reporter: Emily Berk
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 4.2.2
>
>
> Steps to reproduce:
> # Use the /bin/karaf script to start Karaf with the default log configuration file ([https://github.com/apache/karaf/blob/karaf-4.2.1/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg]).
> # Try setting the log level of a package that contains numbers using {{log:set}}:
> {code:java}
> karaf@root()> log:get
> Logger │ Level
> ────────────────────────┼──────
> ROOT │ INFO
> audit │ TRACE
> org.apache.aries.spifly │ WARN
> org.apache.sshd │ INFO
> karaf@root()> log:get org.ops4j.pax.web
> INFO
> karaf@root()> log:set WARN org.ops4j.pax.web
> karaf@root()> log:get org.ops4j.pax.web
> INFO
> karaf@root()> log:get
> Logger │ Level
> ────────────────────────┼──────
> ROOT │ INFO
> audit │ TRACE
> org.apache.aries.spifly │ WARN
> org.apache.sshd │ INFO
> {code}
> _etc/org.ops4j.pax.logging.cfg_ does appear to be updated correctly with two new lines:
> {code:java}
> log4j2.logger.org_ops4j_pax_web.level = WARN
> log4j2.logger.org_ops4j_pax_web.name = org.ops4j.pax.web
> {code}
> I'm not sure if the log level is not set or if the {{log:get}} command just reports the level incorrectly. The issue also occurs for loggers that are configured in _etc/org.ops4j.pax.logging.cfg_ instead of with {{log:set}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)