felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanjeeb Sahoo <sa...@sun.com>
Subject FELIX-2655: allow event admin log level to be configurable
Date Thu, 14 Oct 2010 07:37:55 GMT

I have attached a patch for this issue in JIRA. I would like to know 
from the developers of event admin service if they are fine with the 
change. The change can be described as adding a configuration option to 
control the logger's log level and the default being LOG_WARNING. Hope 
someone will look at it soon.


-------- Original Message --------
Subject: 	[jira] Created: (FELIX-2655) allow event admin log level to be 
Date: 	Wed, 13 Oct 2010 15:53:32 -0400 (EDT)
From: 	Sahoo (JIRA) <jira@apache.org>
Reply-To: 	dev@felix.apache.org
To: 	dev@felix.apache.org

allow event admin log level to be configurable

                  Key: FELIX-2655
                  URL: https://issues.apache.org/jira/browse/FELIX-2655
              Project: Felix
           Issue Type: Bug
           Components: Event Admin
             Reporter: Sahoo
              Fix For: eventadmin-1.2.4

Currently eventadmin bundle prints messages like these:

DEBUG: EventAdmin: org.apache.felix.eventadmin.CacheSize=30

DEBUG: EventAdmin: org.apache.felix.eventadmin.ThreadPoolSize=20

DEBUG: EventAdmin: org.apache.felix.eventadmin.Timeout=5000

DEBUG: EventAdmin: org.apache.felix.eventadmin.RequireTopic=true

In my env, there is no LogService, so the messages appear in System.out. I don't see any way
to disable them from being logged. Should we not make the log level configurable just like
it is done in FileInstall?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message