Hi Nikita, To sum it up: The Configuration Admin logs to the OSGi LogService if one is available. If not, _all_ logging goes to stderr. See the ConfigurationManager.log [1] method.
As soon as you deploy a LogService, it is at the discretion of that service, whether to log any messages and where to record them. For this reason, setting the felix.log.level has no influence at the actual logging level used by the LogService. Hope this helps. Regards Felix [1] http://svn.apache.org/repos/asf/felix/trunk/configadmin/src/main/java/org/apache/felix/cm/impl/ConfigurationManager.java Nikita Sawant schrieb: > Hi Richard, > > Just restating : To disable the DEBUG output, I need to : > > 1. Deploy a Log Service > 2. Set felix.log.level to 3. > > Just (2) is not sufficient ( as I have it set to 3 currently ). > > ~ Nikita > > > Richard S. Hall wrote: >> You can get a snapshot of the simple logger in Felix in the snapshot >> repo: >> >> >> http://people.apache.org/repo/m2-snapshot-repository/org/apache/felix/org.apache.felix.log/0.9.0-SNAPSHOT/ >> >> >> Setting your log level to 3 should do the trick. >> >> -> richard >> >> Nikita Sawant wrote: >>> Thanks! >>> >>> Where can I get a log service implementation. I don't see one here: >>> http://repo1.maven.org/maven2/org/apache/felix/ >>> >>> Also, if I have felix.log.level set to 3 (INFO), then the Config >>> Admin Service should not log DEBUG messages, no? >>> >>> Regards, >>> Nikita >>> >>> Clement Escoffier wrote: >>>> Hi, >>>> >>>> I'm not sure that you can set the log level of the configuration >>>> Admin. To "remove" the traces, deploy a log service. The >>>> configuration admin will use the log service instead of printing >>>> traces. >>>> >>>> Regards, >>>> >>>> Clement >>>> >>>> On 26.01.2009, at 20:49, Nikita Sawant <[email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> I am using the Apache Felix Configuration Admin Service (1.0.4), >>>>> it prints out debug statements to the console : >>>>> >>>>> *DEBUG* Scheduling task Fire ConfigurationEvent: pid=... >>>>> *DEBUG* Running task Fire ConfigurationEvent: pid=... >>>>> *DEBUG* Scheduling task Update: pid=... >>>>> *DEBUG* Running task Update: pid=... >>>>> >>>>> Is there a service property, which I can set to disable debugging? >>>>> If not, is there any other means to disabling the above *DEBUG* >>>>> output ? >>>>> >>>>> Thanks, >>>>> Nikita >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
