I found the reason. The property is set correctly to ERROR in Karaf but the package is started at run level 8. The pax-url-wrap bundle is started at run level 5 before the property for the fallback logger is set to ERROR. This causes the fallback logger to log at default level TRACE. Workaround might be to change run level of wrap to something higher than 8. For plain Karaf 4.2.7 it does work with e.g. 10 but you should't try to activate bundles with wrap with lower run level!
Regards Benjamin On 04.10.2019 16:07, Benjamin Graf wrote: > I think it's "org.ops4j.pax.logging.DefaultServiceLog.level=ERROR" but > not tried yet. > > Regards > > Benjamin > > On 04.10.2019 10:03, J. Brebec wrote: >> Do you remember the name of the property or where I should look ? I didn't >> see anything on this suject in the release note of pax logging. >> >> Thanks >> >> On 2019/10/03 18:01:24, Benjamin Graf <[email protected]> wrote: >>> If I remember right there is a new option to be set since pax-logging 1.11. >>> >>> Might not be set yet in Karaf 4.2.7 >>> >>> Regards >>> Benjamin >>> >>> Am 3. Oktober 2019 13:59:01 MESZ schrieb "J. Brebec" >>> <[email protected]>: >>>> Thanks. >>>> >>>> It's probably related to the upgrade to pax-logging too, but when I >>>> launch Karaf 4.2.7 (on windows), there is a System.println visibile in >>>> the console : >>>> >>>> org.ops4j.pax.url.wrap >>>> [org.ops4j.pax.url.commons.handler.HandlerActivator] DEBUG : Handler >>>> for protocols [wrap] started >>>> >>>> >>>> On 2019/10/03 09:10:43, jbonofre <[email protected]> wrote: >>>>> Let me take a look. It's probably a side effect of pax-logging 1.11 >>>> update. >>>>> I keep you posted. >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> >>>>> >>>>> -- >>>>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html >>>>> >>> -- >>> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
signature.asc
Description: OpenPGP digital signature
