For a while we had Felix' Logger using a LogService instance if one was
available, but this was leading to deadlocks since some logging was
occurring while holding locks and we cannot control what happens when we
call out to a logger. As a result, we disabled this feature until it can
be resolved.
There is still a possibility to get Felix to use a different logger by
passing a Logger instance into Felix' constructor via the configuration
properties, but this would require you to create your own Felix
instance, see the following link for the property description:
http://felix.apache.org/site/apache-felix-usage-documentation.html#ApacheFelixUsageDocumentation-configuringfelix
And the following link on how to launch Felix yourself:
http://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html
-> richard
Jacques-Olivier Goussard wrote:
Hi
Does anybody have an idea about how to capture felix logging in a file ?
The org.apache.felix.framework.Logger class disables LogService logging and
sends
everything to System.out.
The pb is that if felix is used as daemon (background server), logging is
lost.
I can redirect to a file, but I'd rather have all logging in one place (I
use log4j internally) and
inherit all the rollover and log appenders setup.
Any idea to workaround this ?
/jog
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
