October 2011 - logback-user

Re: [logback-user] Logback suddenly stopped logging
by Andreas Dejung 19 Jun '14

19 Jun '14

I had the same problem and I think I know why J Solaris does interrupt IO blocked thread which then causes the OutputStreamAppender to catch the IOException in line 218 (version 0.9.24). I actually run version 0.9.18 but this part has not change so I guess it will behave the same way. If we look at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4385444 InterruptedIOException should not be required by platform specification (sol) And log4j https://issues.apache.org/bugzilla/show_bug.cgi?id=44157 InterruptedIOException ignored by log4j I think it should be solved the same why } catch (InterruptedIOException iioe){ //give the thread a changes to act on interruption and then carry on Thread.currentThread().interrupt(); } catch (IOException ioe) { // as soon as an exception occurs, move to non-started state // and add a single ErrorStatus to the SM. this.started = false; addStatus(new ErrorStatus("IO failure in appender", this, ioe)); } I could not find the jira entry mentioned in this thread therefore I write it here J BTY the jvm option -XX:-UseVMInterruptibleIO does prevent the interruption by solaris but that's only a workaround and not solving the problem ;) Cheers Andy

8 16

(Important) Dynamically change the scan period
by Yihya Hugirat 08 Apr '13

08 Apr '13

hi all, i have migrated to logback to be able to change the log levels dynamically. i'm testing it now with calssfish 3.01 and somehow it is not working when i change the levels in logback.xml there nothing happens. by deploying from netbeans i get the following: |-INFO in ch.qos.logback.classic.turbo.ReconfigureOnChangeFilter@11bfee0 - Will scan for changes in [[C:\Dokumente und Einstellungen\user_Home\Eigene Dateien\NetBeansProjects\WS-LDAP\build\web\WEB-INF\classes\logback.xml]] every 15 seconds. but when i change the levels in this file nothing happens Any help will be appreciated Hugirat -- إِنَّ الَّذِينَ يُحِبُّونَ أَنْ تَشِيعَ الْفَاحِشَةُ فِي الَّذِينَ آمَنُوا لَهُمْ عَذَابٌ أَلِيمٌ فِي الدُّنْيَا وَالآخِرَةِ وَاللَّهُ يَعْلَمُ وَأَنْتُمْ لا تَعْلَمُونَ My public key please use it when you contact me: هذا مفتاحي العام الرجاء أستخدامه عند الإتصال بي: 09BA B710 4B98 ECDA 8C0A 6CB1 2E1E CF88 6A12 F2C3

3 4

Websphere specific JMX configuration?
by Sumanth Donthi 12 Jun '12

12 Jun '12

How can we enable JMX for logback in WebSphere ? Currently do not see ch.qos.logback.classic.jmx.Configurator in jconsole though <jmxConfigurator/> tag exist in logback configuration file. logback 0.9.27 WebSphere 7.0 This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-user/2010-November/001886.html -Sumanth

4 6

Class not found exception for LoggingEventVO
by MDerr＠nycm.com 13 Jan '12

13 Jan '12

I have an application client set up to send a logging message over a bus using a logback JMSQueueAppender. Logback version is 0.9.24 and slf4j version is 1.6.1. This is running on a Websphere 7.0 server in Rational Application Developer 7.5. I've tested the bus and queue with a simple text message using the RAD Universal Test Client and that works fine, so at least the foundation is solid. When I log a message to the message queue, I wind up with the following stack trace under a wide variety of attempts: [8/11/10 14:44:16:223 EDT] 0000002b SystemOut O Exception CWSIA0122E: An exception occurred deserializing a message, exception: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO. [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R javax.jms.MessageFormatException: CWSIA0122E: An exception occurred deserializing a message, exception: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO. [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObject( JmsObjectMessageImpl.java:277) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.csg.logger.mdb.NYCMLoggerMDB.handleMessage(NYCMLoggerMDB.java:45) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.csg.logger.mdb.NYCMLoggerMDB.onMessage(NYCMLoggerMDB.java:36) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.container.MessageEndpointHandler.invokeMdbMethod( MessageEndpointHandler.java:1092) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.container.MessageEndpointHandler.invoke( MessageEndpointHandler.java:777) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at $Proxy42.onMessage(Unknown Source) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint( JmsJcaEndpointInvokerImpl.java:233) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch( SibRaDispatcher.java:900) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run( SibRaSingleProcessListener.java:550) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1550) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R Caused by: java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.LoggingEventVO [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.lang.Class.forNameImpl(Native Method) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.lang.Class.forName(Class.java:136) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.loadClass(WsObjectInputStream.java:227 ) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.access$000(WsObjectInputStream.java:53 ) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream$2.run(WsObjectInputStream.java:191) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.security.util.AccessController.doPrivileged( AccessController.java:118) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.resolveClass( WsObjectInputStream.java:164) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at com.ibm.ws.util.WsObjectInputStream.resolveClass( WsObjectInputStream.java:156) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1591) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1512) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1748) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) [8/11/10 14:44:16:223 EDT] 0000002b SystemErr R at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObjectInternal( JmsObjectMessageImpl.java:345) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsObjectMessageImpl.getObject( JmsObjectMessageImpl.java:271) [8/11/10 14:44:16:239 EDT] 0000002b SystemErr R ... 10 more This always happens when trying to get the message object out of the message in the onMessage code in my message driven bean. For example, the stack dump was generated at the event = . . . line in the code below: if (msg instanceof ObjectMessage){ ObjectMessage objectMesssage = (ObjectMessage) msg; System.out.println("Got ObjectMessage"); event = (ILoggingEvent) objectMesssage.getObject(); } I have the logback classic jar on my classpath successfully because I use a number of other classes from it in my code. If anyone can help with this, I would appreciate it. I can provide additional information as needed. Thanks, Merritt Derr ***CONFIDENTIALITY NOTICE*** This email and any attachments to it are confidential and intended solely for the individual or entity to whom it is addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this email in error, please contact the sender by reply email and destroy all copies of the original message.

3 2

Building logback when tests fail
by Thorbjørn Ravn Andersen 10 Nov '11

10 Nov '11

Hi. I am trying to set up Logback for development in order to write a JDK14Appender (based on the bridge) and my cloned source fails in testing with [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) on project logback-classic: There are test failures. so I cannot run the "mvn package" command listed on the documentation page. Running mvn -Dmaven.test.skip=true package gives me [ERROR] Failed to execute goal on project logback-classic: Could not resolve dependencies for project ch.qos.logback:logback-classic:jar:0.9.30-SNAPSHOT: Could not find artifact ch.qos.logback:logback -core:jar:tests:0.9.30-SNAPSHOT -> [Help 1] instead. I'd like to get this up and running in Eclipse but it is not quite easy even with both egit and Eclipse Maven plugins. What would you suggest me to do to get up and running? Thanks /Thorbjørn

3 11

Logback config from Tomcat - always a static resource, never a scannable file?
by jakartaman 27 Oct '11

27 Oct '11

Hi, I have checked out how to configure logback for Tomcat webapps (as described in http://logback.qos.ch/manual/contextSelector.html) At one point, one configures the name of the XML config file, like so: <env-entry> <description>URL for configuring logback context</description> <env-entry-name>logback/configuration-resource</env-entry-name> <env-entry-type>java.lang.String</env-entry-type> <env-entry-value>logback-app-A.xml</env-entry-value> </env-entry> Unfortunately, the manual suggests (and code inspection confirms) that the XML config file is indeed always a resource on the classpath, never a file on the filesystem. This means the nifty "scan" facility cannot be used in the webapp, as scanning a classpath resource is not exactly fruitful. Before I start adding some code, is there some known way to make the webapp aware of changing XML config files? -- David

1 0

Something which should be made clearer in the logback doc: Should a layout be threadsafe?
by jakartaman 26 Oct '11

26 Oct '11

Hi, Quick remark: It is not clear from the logback docs whether a new layout should be threadsafe. I strongly suspect that it should be (why would logback do the possibly unnecessary locking for you?), but - should that not be explicitly said? E.g. coders may fall into the usual trap of having an instance-bound or even static SimpleDateFormat member and not making the access to it synchronized etc (aehm). Best regards, --- David

2 2

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

Logback fallback behaviour in case auto config fails ...
by jakartaman 25 Oct '11

25 Oct '11

Hi again Noticed that logback basically bails out if none the default configuration resources can be found. I.e. in ch.qos.logback.classic.util.ContextInitializer.autoConfig() -> If an initial resource is *not* found, BasicConfigurator is invoked, -> If an initial resource *is* found, either Groovy Configurator or JoranConfigurator are invoked on the resource depending on their ending. -----> But if I understand correctly, that may fail (e.g. because of bad XML), in which case configuration is left ... unconfigured. Shouldn't the logic be changed to fall back to BasicConfigurator in that case also? Best regards, -- David

2 1

I'm getting the "substitute logger" error message yet my appender still works
by Paul Gifford 24 Oct '11

24 Oct '11

Hi, I've written a custom appender that extends AppenderBase<ILoggingEvent> and put it in a library. I have a webapp that uses the custom appender. When I deploy that webapp to Tomcat I get the SLF4J error message "The following loggers will not work because they were created during the default configuration phase of the underlying logging system." The loggers listed are my custom appender plus the Spring JDBC classes the appender depends on (my appender logs to a table). My appender, however, works just fine. I get entries in my table just as expected. Is this error message something to be concerned about or am I receiving it in error? Thanks, Paul

3 10