Custom based on 3.0.3. does not reproduce with 3.0.3 plain/vanilla/outofthebox. I deleted all bundles with start level >= 50 but still reproduces. In terms of a diff after deleting, there are 128 (custom) vs 64 (3.0.3) bundles with start level < 50. I tried to delete this thread yesterday so you can ignore it, I'll determine which bundle(s) is/are causing the problem.
btw, I tried using the original org.ops4j.pax.logging.cfg file from 3.0.3 and still reproduces with custom distro (based on 3.0.3). jbonofre wrote > Did you change something in etc/org.ops4j.pax.logging.cfg and > pax-logging bundles are correctly started ? > > Do you use a custom distro ? > > I just tested with a fresh Karaf 3.0.3 and it starts fine, including > pax-logging. > > Regards > JB > > On 05/19/2015 10:50 PM, asookazian2 wrote: >> Karaf 3.0.3 >> >> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". >> SLF4J: Defaulting to no-operation (NOP) logger implementation >> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further >> details. >> >> Please add a JIRA to specify which bundle(s) is/are causing this problem, >> I >> see nothing logged in the karaf.log either. thx. >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/SLF4J-logging-error-in-console-on-startup-tp4040505.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> > > -- > Jean-Baptiste Onofré > jbonofre@ > http://blog.nanthrax.net > Talend - http://www.talend.com -- View this message in context: http://karaf.922171.n3.nabble.com/Re-SLF4J-logging-error-in-console-on-startup-tp4040511p4040522.html Sent from the Karaf - User mailing list archive at Nabble.com.
