October 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

Removal of LoggerContext constant in 0.9.17
by Chad La Joie 21 Oct '09

21 Oct '09

I was just updating the version of logback used by my project and I got an error. It appears that the constant LoggerContext.ROOT_NAME has been removed however I don't see any mention of this in the release notes. Was this intentional? If so, what is the correct way to retrieve the root logger now? -- SWITCH Serving Swiss Universities -------------------------- Chad La Joie, Software Engineer, Net Services Werdstrasse 2, P.O. Box, 8021 Zürich, Switzerland phone +41 44 268 15 75, fax +41 44 268 15 68 chad.lajoie(a)switch.ch, http://www.switch.ch

2 2

Which Appender strategy for this need ? [C1]
by Christophe LALLEMENT 14 Oct '09

14 Oct '09

Hello I have a simple logging strategy but i'm not able to find a good logback configuration to get the right result. My context: -> an application which is started (and killed) every day (and run several hours, but not more that 1 day) My Need -> keep 5 days of log history (into 5 files or 5 directory with files ..) -> if possible zip/gzip history files -> several intraday run must log into the same file. -> if possible, current log file is not versionned with date prefix (or directory specific structure). What i understand after reading logback documentation: 1/ use of file name which contains day information => OK but history are not managed (and no more compression) 2/ Rolling appender => Seems to not work because timebasedrolling policy suppose that process run many daus without stopping Is it right ? Is there a solution ? if not which is the best approach. Thx Regards Christophe Lallement Technical Architect ITEC/IBD/DAI 17, cours Valmy 92800 Puteaux Tel.: +33 (0)1.42.13.94.21 christophe.lallement(a)sgcib.com ************************************************************************* This message and any attachments (the "message") are confidential, intended solely for the addressee(s), and may contain legally privileged information. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ************ Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. *************************************************************************

1 0

JMX Triggered Rollover
by Tom Liu 13 Oct '09

13 Oct '09

Hi, In certain cases, people want to trigger a rollover via jmx. It seems jmx tirggered rollover is not supported now, would you please consider implementing this feature? Thanks in advance! Best Regards, Tom

1 0

Feature question
by Ayman Hammoudeh 07 Oct '09

07 Oct '09

Hello, Is there a way to get the thread-ID in the layout pattern in xml configuration. Regards, Ayman Hammoudeh

3 8

log4j/logback/JCL/SLF4J???
by David Vergnaud 06 Oct '09

06 Oct '09

Hi everyone! I have a very general question about logging in Java -- I appreciate this being a logback-related list, but I assumed people with lots of experience in this domain would be able to give me the good advice I need :-) I want to include logging in the framework I'm creating -- this include several different modules that share centralized services like authentication, configuration, and, soon, logging. I've tried using log4j, but it didn't really fit my purpose, or rather I couldn't make it fit my purpose -- unresolved bugs and stuff. Be it as it may, I think I have to move on to a new library, only I'm wondering which one I should use. Perhaps someone can help me decide? My goal is to have logs written in an abstract, language-independent way (level, timestamp, message ID and name/value parameter pairs), so they can be displayed e.g. in different languages (e.g. in a web interface). For this, I want to use XML as the basis format for the logs. Ideally, logs should be rotated, with each finished file being a valid XML document by itself (i.e. with wrapping tag, would've worked in log4j if the writeFooter() method had been called in FileAppender.closeFile() ). It is quite clear to me that the current log file will probably *not* be a proper XML document (no end tag), but I'll take care of that later. I might also consider being happy with having invalid XML log files (no wrapping tag) and including them in a wrapper file using a SYSTEM entity. I'll see. Also ideally, if possible, I'd like to have a system that allows setting the log level on a medium basis -- i.e. have the very same message, from the very same logger, be logged only on channels for which the log level is enabled. For instance, I'd like to be able to use a single logger (in the log4j sense) with one console channel and one file channel, and have the file channel record all levels (debug - error) while the console displays only e.g. info to error. AFAIK this wasn't possible with log4j, as the logging level was defined for each logger, and the logger itself decided for all appenders whether a message should be logged or not. I don't mind expanding a bit on an existing library, but I'd like most of the functionality I've just described to be readily available or at least foreseen. Does anyone have a good idea? Thanks a lot in advance! Pagod

3 3

LoggerContext.shutdownAndReset() ?
by Rob Ross 05 Oct '09

05 Oct '09

Hi there. I just d/l version 0.9.17. Previously I was using 0.9.11, classic & core jars. The method LoggerContext.shutdownAndReset() doesn't seem to exist any more. Has this been deprecated? Or renamed? What is the replacement method to use? Thanks, Rob

2 1

Messages from multiple senders interleaved on one line
by Michael Olson 02 Oct '09

02 Oct '09

Hello all, I'm new to logback, and I'm trying out a configuration that is, more or less, a word-for-word transcription of an example configuration from the documentation; you can view the configuration here: http://logback.pastebin.com/m1a6f2875 I'm having problems where I'm getting interleaved messages on a single line. I don't believe this is expected behavior, and it certainly makes it harder to understand what's going on. I've tried searching the mailing list and bug list to no avail. Here's an example from one log file: 2009-09-30 15:45:31,649 [Thread-5] INFO CalaisSubmitter - CalaisFeedSubmitter clean shutdown 2009-09-30 15:45:33,2302009-09-30 15:45:33,230 [ [Thread-15] INFO PostItemSubmitter - Shutdown aborted queue operation Thread-19] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:45:33,231 [2009-09-30 15:45:33,231Thread-17] [ INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:45:33,231 [2009-09-30 15:45:33,231Thread-17] [Thread-21] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:45:34,230 [main] INFO Eventweb - All stopped and here's an example from another log file: 2009-09-30 15:47:10,061 [Thread-5] INFO CalaisSubmitter - CalaisFeedSubmitter clean shutdown 2009-09-30 15:47:11,3782009-09-30 15:47:11,378 [ [2009-09-30 15:47:11,378 [Thread-15] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:47:11,3782009-09-30 15:47:11,378 [ [2009-09-30 15:47:11,378 [Thread-15]Thread-21]Thread-17] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:47:11,3782009-09-30 15:47:11,378 [ [2009-09-30 15:47:11,378 [Thread-15]Thread-21] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:47:11,378 [Thread-19] INFO PostItemSubmitter - Shutdown aborted queue operation 2009-09-30 15:47:12,378 [main] INFO Eventweb - All stopped Can anyone tell me why I'm getting interleaved messages, and what I might be able to do to prevent this from happening? Thanks, - Michael

4 3

urgent explination issue
by Ayman Hammoudeh 01 Oct '09

01 Oct '09

Hello, I want to know how can I use max history in Size and time based archiving<http://logback.qos.ch/manual/appenders.html#SizeAndTimeBasedFNATP> and where exactly to put the<MaxHistory> tag in the xml , I have tried to put it in the <RollingPolisy> tag but its not working. Any help would be appreciated. Best Regards, Ayman Hammoudeh

3 6

Log only one java package
by alex 01 Oct '09

01 Oct '09

Hi, how is possible to log ONLY the log message for one specified java package ? For example I have to log only the log call from com.test.mypack.* classes. Do I have to write a filter ? Thanks a lot for all help

2 2