You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@karaf.apache.org by Paul Spencer <pa...@mindspring.com> on 2020/12/10 23:42:52 UTC

Setting the log level to DEFAULT for a logger does not remove the logger

Karaf 4.2.9
Setting the log level to DEFAULT for a logger results with a level of 'blank' when it is expected the logger would be removed from the list. Looking in etc/org.ops4j.pax.logging.cfg I see an entry for the logger, log4j2.logger.foo_bar.name, but no corresponding log4j2.logger.foo_bar.level entry.  In Karaf 3.x, setting a logger to default removed all corresponding entries from etc/org.ops4j.pax.logging.cfg.


Should the command  "log:set DEFAULT foo.bar" remove all corresponding entries in  etc/org.ops4j.pax.logging.cfg?

***
* Example of issue
***
karaf@root()> log:get
Logger                  │ Level
────────────────────────┼──────
ROOT                    │ INFO
audit                   │ TRACE
org.apache.aries.spifly │ WARN
org.apache.sshd         │ INFO
karaf@root()> log:set debug foo.bar
karaf@root()> log:list
Logger                  │ Level
────────────────────────┼──────
ROOT                    │ INFO
audit                   │ TRACE
foo.bar                 │ DEBUG
org.apache.aries.spifly │ WARN
org.apache.sshd         │ INFO
karaf@root()> log:set DEFAULT foo.bar
karaf@root()> log:get
Logger                  │ Level
────────────────────────┼──────
ROOT                    │ INFO
audit                   │ TRACE
foo.bar                 │
org.apache.aries.spifly │ WARN
org.apache.sshd         │ INFO
karaf@root()> 


***
* etc/org.ops4j.pax.logging.cfg
***
log4j2.logger.foo_bar.name = foo.bar

Paul Spencer