directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John E. Conlon" <jcon...@verticon.com>
Subject Re: [jira] Created: (DIRSERVER-611) An OSGi Activator can allow simple way for reconfiguration of log4j.properties without restarting the JVM.
Date Fri, 28 Apr 2006 14:55:14 GMT
On Fri, 2006-04-28 at 00:54 -0400, Enrique Rodriguez wrote:
> John Conlon (JIRA) wrote:
> ...
> >   private static final String LOG_PROPERTIES_LOCATION =  
> >    "log4j.configuration";
> 
> Was this intentional ^^^ to use 'configuration' as the extension?  In 
> the comment, below, you use props.  
Yes it was intentional. As you mentioned in a previous email the
standard way to pass log4j configuration was with a command line like:
java -Dlog4j.configuration=file://$(pwd)/conf/log4j.properties -jar
bin/felix.jar

Earlier version of felix required a property in the config.properties
file to pass system properties through to bundles. I used one like this.

log4j.configuration=${log4j.configuration}

Recent version of felix seem to 'pass' the system property through to
the bundles with out need for the pass through property in
config.properties so I just commented out the above property and use the
command line. If I want to hard code the location I can just uncomment
the property and use it, without putting it in the startup script.

> This why your SCR logging died?
All other non-scr bundles continued to log to the console (including the
apacheDS backend) but not the one bundle I tested with scr.  After I
changed that bundle back to servicebinder it then sent its logs (and
System.out.println just fine.

regards,
John






Mime
View raw message