I solved my problem. The issue was that pax-logging and log4j are not immediately ready after pax logging api and service bundle started. They need some time (1-3 seconds).
I installed and started bundles one by one, and some bundles stated they logging before pax-logging was ready - that's why I got DEBUG messages when I didn't want to get them. Now I changed the sequence of bundle management and everything seems to be fine. Are my explanations of the problem right? On Wednesday, 24 August 2016 23:44:55 UTC+3, iJava wrote: > > Hi all, > > Could someone explain 1)what is org.ops4j.pax.logging.DefaultServiceLog , > 2) how it is related with my configs for log4j and 3) what values > it can have besides WARN and INFO. > > I ask, because when I don't set it via system parameter to WARN OR INFO I > get about 56000 lines of DEBUG. > Even if I set it to FATAL I anyway get 56000 lines in log of DEBUG. > -- -- ------------------ 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]. For more options, visit https://groups.google.com/d/optout.
