Global logging reconfiguration results in configuration error
-------------------------------------------------------------
Key: SLING-529
URL: https://issues.apache.org/jira/browse/SLING-529
Project: Sling
Issue Type: Bug
Components: Commons Log
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: 2.0.1
After the implementation of SLING-525, the global logging configuration does
not work any more. Instead a ConfigurationException is thrown and logged:
13.06.2008 07:44:22.647 *ERROR* [Configuration Updater]
org.apache.felix.configadmin Updating configuration property
org.apache.sling.commons.log.names caused a problem: Missing categories in
configuration org.apache.sling.commons.log.LogManager
(org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names
: Missing categories in configuration org.apache.sling.commons.log.LogManager)
org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names
: Missing categories in configuration org.apache.sling.commons.log.LogManager
at
org.apache.sling.commons.log.slf4j.LogConfigManager.updateLoggerConfiguration(LogConfigManager.java:388)
at
org.apache.sling.commons.log.LogManager$GlobalConfigurator.updated(LogManager.java:180)
at
org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1125)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:90)
The problem seems to be that there is no acceptable entry for the logger names
in the global configuration, whereas this setting should be "" indicating the
"ROOT" logger meaning apply to all loggers as a default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
