Re: Blueprint and managed Services

2017-12-12 Thread Guillaume Nodet
Here's a typical example of using configuration in blueprint: https://github.com/apache/karaf/blob/karaf-2.x/shell/ssh/src/main/resources/OSGI-INF/blueprint/shell-ssh.xml The pid of the configuration is defined using the persistent-id attribute:

Re: custom log file size not restricted

2017-12-12 Thread Jean-Baptiste Onofré
Hi, It should work (it's what we are using without problem for "out" appender). I guess you added this appender in the logger (rootLogger or specific logger) right ? Can you try to remove extra spaces around '=' ? Regards JB On 12/13/2017 07:05 AM, jyothi wrote: Hi, I have configured for

custom log file size not restricted

2017-12-12 Thread jyothi
Hi, I have configured for a custom log in pax logging in Karaf as follows and found the size of the custom log is not restricted to 1 MB and increasing. Can you please let us know what could be the issue? Thanks in advance log4j.appender.custom = org.apache.log4j.RollingFileAppender

Blueprint and managed Services

2017-12-12 Thread Guenther Schmidt
Hello, how do I set the system.pid for a service that needs to receive its configuration data from the OSGi container using Blueprint? Guenther