I have created PAXLOGGING-274 <https://ops4j1.jira.com/browse/PAXLOGGING-274>
Thanks ! Le vendredi 4 octobre 2019 16:20:08 UTC+2, Jérémie Brébec a écrit : > > Hello, > > I am upgrading to Karaf 4.2.7 with Pax Logging 1.11 > > Everytime Karaf is started, I see this line in the console : > > org.ops4j.pax.url.wrap [org.ops4j.pax.url.commons.handler.HandlerActivator] > DEBUG : Handler for protocols [wrap] started > > > I use a custom distribution with the static framework : the > startup.properties file is generated, and the start-level of pax.url.wrap > is lower than the start level of pax-logging-api > As it starts before the pax-logging-api, it gets a "fallback logger" which > log with System.out.println() > > 1/ I can't change the threshold of this logger, because the property > "org.ops4j.pax.logging.DefaultServiceLog.level" is read only when the > pax-loggin-api is started > 2/ I can't use a "FileServiceLogger" as a fallback because the > pax-url-wrap bundle is not starting (the logger is loaded in the activator > class, before the activator is called) > 3/ I can use a BufferingLog. However, this function doesn't seem to be > fully implemented : the queue in this logger is never flushed/cleared. > > Is there a solution to my problem without patching the startup.properties > or the karaf features ? > > Regards, > Jérémie > > -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/6cd16d32-880a-4ff2-acef-7b0061bc91f4%40googlegroups.com.
