Robert Munteanu created SLING-6624:
--------------------------------------
Summary: LogConfigManager reports incorrect config pid when
duplicate categories are defined
Key: SLING-6624
URL: https://issues.apache.org/jira/browse/SLING-6624
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons Log 5.0.0
Reporter: Robert Munteanu
Assignee: Robert Munteanu
Fix For: Commons Log 5.0.2
When a LogManager factory configuration that includes an already defined
category name is processed, the LogConfigManager throws an exception, for
instance:
{noformat}Updating property org.apache.sling.commons.log.names of configuration
org.apache.sling.commons.log.LogManager.factory.config.edfcfd90-27fa-4cfb-a276-b52247e3dc53
caused a problem: Category com.day.cq.compat.codeupgrade already defined by
configuration
org.apache.sling.commons.log.LogManager.factory.config.edfcfd90-27fa-4cfb-a276-b52247e3dc53
(org.osgi.service.cm.ConfigurationException:
org.apache.sling.commons.log.names : Category com.day.cq.compat.codeupgrade
already defined by configuration
org.apache.sling.commons.log.LogManager.factory.config.edfcfd90-27fa-4cfb-a276-b52247e3dc53)
org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names
: Category com.day.cq.compat.codeupgrade already defined by configuration
org.apache.sling.commons.log.LogManager.factory.config.edfcfd90-27fa-4cfb-a276-b52247e3dc53{noformat}
However, this does not include the pid of the existing configuration, but the
new one, which makes debugging harder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
