Logging config broken?

[Alexander Klimetschek]

Hi,

I wanted to set Sling's general log level to DEBUG, but it stays at
INFO level, no matter what I do. I tried to change sling.properties to

org.apache.sling.commons.log.intialize = true
org.apache.sling.commons.log.level = DEBUG

and restarted the server. I also set the configuration in the sling
console under "Sling Logging Logger Configuration", where log level is
now DEBUG (config is persisted), but nothing changed.

Is this just a misconfiguration due to changes by
http://issues.apache.org/jira/browse/SLING-525 or a bug?

Regards,
Alex

[Alexander Klimetschek]

And I also changed the (new or old?) config in the management console
under "Sling Logging Configuration" to DEBUG. Did not help either.

I am confused... my console configuration contains these entries
related to logging. Note the duplicates:

Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)
Sling Logging Writer Configuration
(org.apache.sling.commons.log.LogManager.factory.writer)
...
Sling Logging Configuration (org.apache.sling.commons.log.LogManager)
Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)
Sling Logging Writer Configuration
(org.apache.sling.commons.log.LogManager.factory.writer)

I want my log4.properties/xml back ;-)

Regards,
Alex

[Felix Meschberger]

Hi,

Sorry for the confusion. This is caused by broken the Configuration
Admin plugin of the Web Console being broken. There have already been
submitted a list of bugs with respect to this plugin and I am currently
working on rewriting this plugin.

Regards
Felix

Post by Alexander Klimetschek
And I also changed the (new or old?) config in the management console
under "Sling Logging Configuration" to DEBUG. Did not help either.
I am confused... my console configuration contains these entries
Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)
Sling Logging Writer Configuration
(org.apache.sling.commons.log.LogManager.factory.writer)
...
Sling Logging Configuration (org.apache.sling.commons.log.LogManager)
Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)
Sling Logging Writer Configuration
(org.apache.sling.commons.log.LogManager.factory.writer)
I want my log4.properties/xml back ;-)
Regards,
Alex

[Felix Meschberger]

Hi,

Post by Alexander Klimetschek
Hi,
I wanted to set Sling's general log level to DEBUG, but it stays at
INFO level, no matter what I do. I tried to change sling.properties to
org.apache.sling.commons.log.intialize = true

Logging is always configured. This property is ignored (and support for
it has been removed).

Post by Alexander Klimetschek
org.apache.sling.commons.log.level = DEBUG

This should actually do the trick on setting DEBUG level on restart -
unless some other log level is declared on the command line or system
properties.

Post by Alexander Klimetschek
and restarted the server. I also set the configuration in the sling
console under "Sling Logging Logger Configuration", where log level is
now DEBUG (config is persisted), but nothing changed.

This should do the trick.

Post by Alexander Klimetschek
Is this just a misconfiguration due to changes by
http://issues.apache.org/jira/browse/SLING-525 or a bug?

I checked it out right now and get the following dump in my log:

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)

So, this is definitely a bug. SLING-529.

Thanks for reporting.

Regards
Felix

[Felix Meschberger]

Post by Felix Meschberger
So, this is definitely a bug. SLING-529.

Fixed in Rev. 667371

Regards
Felix

[Alexander Klimetschek]

Thanks, it works now. Only changing "Sling Logging Configuration
(org.apache.sling.commons.log.LogManager)" worked, changing the log
level in "Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)" did have no
effect.

Regards,
Alex

Post by Felix Meschberger

Post by Felix Meschberger
So, this is definitely a bug. SLING-529.

Fixed in Rev. 667371
Regards
Felix

[Felix Meschberger]

Hi,

Post by Alexander Klimetschek
Thanks, it works now. Only changing "Sling Logging Configuration
(org.apache.sling.commons.log.LogManager)" worked,

This is the global configuration

Post by Alexander Klimetschek
changing the log
level in "Sling Logging Logger Configuration
(org.apache.sling.commons.log.LogManager.factory.config)" did have no

This is a factory configuration support which I built in yesterday. This
is still to be documented....


Regards
Felix

Post by Alexander Klimetschek
effect.
Regards,
Alex

Post by Felix Meschberger

Post by Felix Meschberger
So, this is definitely a bug. SLING-529.

Fixed in Rev. 667371
Regards
Felix