February 2009 - logback-user

org.slf4j.impl.StaticLoggerBinder.SINGLETON
by Rusty Wright 25 Oct '11

25 Oct '11

I'm unable to create a bugzilla account at http://bugzilla.slf4j.org/createaccount.cgi Could someone enter this bug report for me? If I change my version of logback to 0.9.11 I don't get this. I get it when I use logback version 0.9.13. I'm using version 1.5.5 of slf4j. Thanks Running TestSuite org.apache.maven.surefire.booter.SurefireExecutionException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest; nested exception is org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest org.testng.TestNGException: Cannot instantiate class edu.berkeley.ist.cars.net.email.EmailTest at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:35) at org.testng.internal.ClassHelper.createInstance(ClassHelper.java:330) at org.testng.internal.ClassImpl.getDefaultInstance(ClassImpl.java:62) at org.testng.internal.ClassImpl.getInstances(ClassImpl.java:81) at org.testng.internal.TestNGClassFinder.<init>(TestNGClassFinder.java:114) at org.testng.TestRunner.initMethods(TestRunner.java:281) at org.testng.TestRunner.init(TestRunner.java:227) at org.testng.TestRunner.init(TestRunner.java:189) at org.testng.TestRunner.<init>(TestRunner.java:138) at org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:477) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:244) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:821) at org.testng.TestNG.runSuitesLocally(TestNG.java:788) at org.testng.TestNG.run(TestNG.java:708) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:62) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:141) at org.apache.maven.surefire.Surefire.run(Surefire.java:177) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:338) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:997) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.testng.internal.ObjectFactoryImpl.newInstance(ObjectFactoryImpl.java:26) ... 23 more Caused by: java.lang.IllegalAccessError: tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory at org.slf4j.LoggerFactory.staticInitialize(LoggerFactory.java:83) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:73) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:272) at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.<init>(AbstractTestNGSpringContextTests.java:77) at edu.berkeley.ist.cars.net.email.EmailTest.<init>(EmailTest.java:21) ... 28 more

4 5

TimeBasedRollingPolicy
by Lang, Johannes 18 Mar '09

18 Mar '09

Hello, i'm trying to get a RollingFileAppender with a TimeBasedRollingPolicy working, but i don't succeed. Here's my Appender-Configuration (which i copied from the logback-manual; only changed the layout): <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <File>logFile.log</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>logFile.%d{yyyy-MM-dd_HH-mm}.log</FileNamePattern> </rollingPolicy> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</Pattern> </layout> </appender> And this is some of the debug-output from the Joran-Configurator: 09:06:48,703 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 09:06:48,734 |-INFO in ch.qos.logback.core.joran.action.NestedComponentIA - Pushing component [rollingPolicy] on top of the object stack. 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Adding parent to RollingPolicy: FILE 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No compression will be used 09:06:48,734 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern logFile.%d{yyyy-MM-dd_HH-mm}.log for the active file 09:06:48,750 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - The date pattern is 'yyyy-MM-dd_HH-mm' from file name pattern 'logFile.%d{yyyy-MM-dd_HH-mm}.log'. 09:06:48,750 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Roll-over every minute. 09:06:48,750 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: logFile.log 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [FILE] from the object stack 09:06:48,750 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to TRACE 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [stout] to Logger[root] 09:06:48,750 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[root] 09:06:48,750 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. Everything seems correct. "Roll-over every minute" is just what i want to do. But what really happens is, that all logging is written to the file "logFile.log". There is no rollover. Any suggestions what's wrong with my appender-config? Cheers Johannes

3 3

Please someone explain %c layout pattern to me
by Lukas Zapletal 02 Mar '09

02 Mar '09

I cant clearly understand the documentation of the conversion word %c http://logback.qos.ch/manual/layouts.html I thought %c{10} will always return string at maximum length 10 but its obviously not true. In the JUnit test "hello.world" is abbreviated "h.world" while length set to 1. Seems its a maximum length of the string before the last dot?!? Thanks ----- -- Lukas Zapletal http://lukas.zapletalovi.com -- View this message in context: http://www.nabble.com/Please-someone-explain--c-layout-pattern-to-me-tp2224… Sent from the Logback User mailing list archive at Nabble.com.

3 3

SLF4J: The following loggers will not work because...
by Jenny 01 Mar '09

01 Mar '09

Hi, Anybody seen this error before? Could you help me figure out what's wrong? ClassA, ClassB, ClassC are not logging anything. SLF4J: The following loggers will not work becasue they were created SLF4J: during the default configuration phase of the underlying logging system. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger SLF4J: com.company.mycode.ClassA SLF4J: com.company.mycode.ClassB SLF4J: com.company.mycode.ClassC thanks, Jenny

2 1

SLF4J: The following loggers will not work because...
by Jenny 28 Feb '09

28 Feb '09

Hi, Anybody seen this error before? Could you help me figure out what's wrong? ClassA, ClassB, ClassC are not logging anything. SLF4J: The following loggers will not work becasue they were created SLF4J: during the default configuration phase of the underlying logging system. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger SLF4J: com.company.mycode.ClassA SLF4J: com.company.mycode.ClassB SLF4J: com.company.mycode.ClassC thanks, Jenny

1 0

SLF4J: The following loggers will not work because...
by Jenny 28 Feb '09

28 Feb '09

Hi, Anybody seen this error before? Could you help me figure out what's wrong? ClassA, ClassB, ClassC are not logging anything. SLF4J: The following loggers will not work becasue they were created SLF4J: during the default configuration phase of the underlying logging system. SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger SLF4J: com.company.mycode.ClassA SLF4J: com.company.mycode.ClassB SLF4J: com.company.mycode.ClassC thanks, Jenny

1 0

Logging from different threads
by Lukas Zapletal 27 Feb '09

27 Feb '09

Hello, I have application with 4 threads called M, 1, 2 and 3. Its using Logback over slf4j in normal way: final static Logger logger = LoggerFactory.getLogger(TheClass.class); I have this configuration: <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>DEBUG</level> </filter> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%d{HH:mm:ss} [%thread] %-5level %logger{20} - %msg%n</Pattern> </layout> </appender> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>TRACE</level> </filter> <File>../../build/puma-gentest1-log.txt</File> <Append>false</Append> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%-5level: %msg (%d{HH:mm:ss} [%thread] %logger{35}) %n</Pattern> </layout> </appender> <root> <level value="TRACE" /> <appender-ref ref="STDOUT" /> <appender-ref ref="FILE" /> </root> <logger name="freemarker.cache"> <level value="INFO" /> </logger> </configuration> The problem: I cannot see error messages logged by one of "worker" threads. I have no clue why. Its not from freemarker.cache package - its different package (com.pike.blabla). ----- -- Lukas Zapletal http://lukas.zapletalovi.com -- View this message in context: http://www.nabble.com/Logging-from-different-threads-tp22229676p22229676.ht… Sent from the Logback User mailing list archive at Nabble.com.

2 10

Dale Chapman is out of the office.
by Dale.Chapman＠medavie.bluecross.ca 27 Feb '09

27 Feb '09

I will be out of the office starting 25/02/2009 and will not return until 09/03/2009. I will be out of the office, on vacation, from February 26th returning on March 9th. Please contact Darren Swansburg for all matters related to the SOA Pilots. Please contact Marc Arsenault for all matters related to Reference Architecture and Common Code. Thanks. ----------------------------------------------------------------------- This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal, and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply. Thank you. La présente communication, y compris toute pièce qui y a été jointe, est destinée uniquement à la personne ou à l’entité à laquelle elle a été adressée, et contient des renseignements à caractère confidentiel et personnel. Toute diffusion ou reproduction non autorisée ou toute intervention entreprise relativement à son contenu est strictement interdite. Si vous avez reçu ce message par erreur, veuillez nous le signaler immédiatement afin que nous puissions effectuer la correction à nos dossiers. Veuillez par la suite supprimer ou détruire le contenu de la transmission originale ainsi que toute réponse ultérieure. Merci. -----------------------------------------------------------------------

1 0

Error counter appender
by Lukas Zapletal 26 Feb '09

26 Feb '09

Hello, I need to count number of error messages coming thru SLF4J into my app and integrate this number with System.exit() call at the end of the program. I have found that best solution would be to write an appender and dynamicaly add it in the code of my application. I am configuring logging by calling LoggerConfigurer (loading XML file) but I do not want to have my appender in this configuration - I do want to configure it dynamically not allowing user to modify XML and disable this error counter appender. But this does not work - the new appender method append() is never called. I think there is a problem with context or something. Here is the code: public class Test { final org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(Test.class); public void main(String[] args) { String fileName = "myfile.xml"; LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); // the context was probably already configured by default configuration // rules lc.shutdownAndReset(); configurator.doConfigure(fileName); ErrorCounterAppender errAppender = new ErrorCounterAppender(); Logger root = LoggerFactory.getLogger(LoggerContext.ROOT_NAME); errAppender.setContext(lc); errAppender.start(); ((ch.qos.logback.classic.Logger) root).addAppender(errAppender); logger.error("TEST"); logger.info("Number of errors: {}", errAppender.getErrorNumber()); // prints 0 System.exit(errAppender.getErrorNumber()); // returns 0 (instead of 1) } catch (Throwable t) { logger.warn("Cannot configure logger from location " + fileName, t); } StatusPrinter.print(lc); } } I think there must be some problem in the context or something. Or is there any better solution of my problem? Here is my appender: /** * Thread-safe implementation of error counter appender for LogBack. */ public class ErrorCounterAppender extends AppenderBase<LoggingEvent> { AtomicInteger errorCounter = new AtomicInteger(0); private Layout<LoggingEvent> layout; public ErrorCounterAppender() { } @Override public void setLayout(Layout<LoggingEvent> layout) { this.layout = layout; } public void resetErrorNumber() { errorCounter.set(0); } public int getErrorNumber() { return errorCounter.get(); } @Override public void start() { if (this.layout == null) { addError("No layout set for the appender named [" + name + "]."); return; } super.start(); } @Override public void append(LoggingEvent event) { if (event == null) return; if (Level.ERROR == event.getLevel()) { errorCounter.incrementAndGet(); } } } ----- -- Lukas Zapletal http://lukas.zapletalovi.com -- View this message in context: http://www.nabble.com/Error-counter-appender-tp22205463p22205463.html Sent from the Logback User mailing list archive at Nabble.com.

2 4

Logback release notes
by Silvano Maffeis 26 Feb '09

26 Feb '09

Hi. Are there logback release notes somewhere? Essentially I would like to know which bugs have been fixed in a new release. Unfortunately the JIRA tickets do not provide this information either, it appears. Cheers, Silvano

2 1