May 2011 - logback-user - mailman3.qos.ch

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

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

use of java.io.File in logback / Android
by Robert Schmid 08 Jul '11

08 Jul '11

I am about to implement an appender that I can use on Android. I'm guessing it won't be much more difficult than doing the same from log4j. The primary problem is that we can't really use java.io.File to access the file system. Android has its own File access API. I believe that this will be as simple as extending RollingFileAppender and overriding methods as needed to swap out the File access apis. Can anybody spot the flaw in my thinking? Are there other pitfalls I need to worry about? Robert Schmid robertschmid(a)airstriptech.com<mailto:robertschmid@airstriptech.com> [cid:image001.jpg@01CB3406.9303A990] www.airstriptech.com<http://www.airstriptech.com/>

3 3

using logback in an API w/o impacting other applications
by Richard Sand 07 Jun '11

07 Jun '11

Hi all, In an API I had to write for a client to interface with an COTS application, I used log4j to bridge to the COTS application's log capability. To totally isolate the usage of log4j in the API I created a wrapper around a Logger with its own Hierarchy. I'm wondering if there is an analogous mechanism for accomplishing this in logback. public final class AgentLogger { public static Hierarchy heirarchy = new Hierarchy(new RootLogger(Level.TRACE)); private Logger wl = null; /** * Private constructor * * @param name */ private AgentLogger (String name) { wl = heirarchy.getLogger(name); wl.setAdditivity(false); } Any advice appreciated. Thanks! Best regards, Richard Sand | CEO 239 Kings Highway East | Haddonfield | New Jersey 08033 | USA Mobile: +1 267 984 3651| Office: +1 856 795 1722| Fax: +1 856 795 1733 <http://www.skyworthttg.com/>

2 3

Logback configuration in Virgo OSGi container
by mvwinsen 31 May '11

31 May '11

Hi, i'm trying to get logback logging working in my Virgo OSGi container. Doing this i'm having some difficulties logging to the rootLogger. Virgo is delivered with a serviceability.xml (which is a renamed logback.xml file). I want to have 'one' logconfiguration (preferabably the serviceability.xml) used by all bundles inside the container. Therefore i've set the VM arg -Dlogback.configurationFile=./config/serviceability.xml. So that the default log configuration is read from that file. When i start the container i see that the logging configuration is setted by default to the ./config/serviceablity.xml (i can see this because i've set the debug to true in the configuration tag of the xml file). In that configuration i've set the root level to info (see file below): <configuration debug="true" scan="true"> <jmxConfigurator/> <appender name="GENERAL" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>./serviceability/logs/GeneralTest.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>./serviceability/logs/General.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>5</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>5MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%-5p %d{ISO8601} [%18.18t] %50.50c : %m%n</pattern> </encoder> </appender> <root level="INFO"> <appender-ref ref="GENERAL" /> </root> </configuration> The problem that i'm facing it that when i ask log4j-over-slf4j to get a logger via the code, then the bundle is falling back to the default configuration of logback (not the one set via the VM args, and therefore is logging console of my Eclipse environment. And nothing to the log file. org.apache.log4j.Logger log; log = Logger.getLogger("logger1"); log.error("test123"); The strange thing is that when i add the above descibed logback.xml configuration to the bundle where i'm trying to log (src/main/resources/logback.xml), then the root logger is linked to the logfile and de log line is outputted to the file. Does anyone has an idea what i'm doing wrong? My goal is to set the logconfigation once as VM arg and just call the Logger.GetLogger('id') of any bundle in the container and log the line to the root logger which is descibed in the logconfiguration. Thanks in advance, Mark -- View this message in context: http://old.nabble.com/Logback-configuration-in-Virgo-OSGi-container-tp31743… Sent from the Logback User mailing list archive at Nabble.com.

2 1

Problems with MDC's inheritance
by Lóránt Pintér 31 May '11

31 May '11

Hi, AFAIK, Log4J's MDC had no inheritance between threads -- this is a new feature introduced in Logback. However, when you are using thread pools, this new feature can cause a lot of trouble, especially when moving to Logback from a different logging system. Consider the following situation: you have a web application where you use the MDC to keep track of which user is logged in. You do certain things on the request processing thread. There are other certain things that you want to execute "in the background". You want to print the originating user's name in the logs for both "foreground" and "background" tasks. In such a case the Runnable's you place on the thread pool's queue need to take care of retaining the MDC from the originating thread. If you do this, and do this in every instance, no problem. However, it happens that you forget to do this. In such a case, with Log4J's non-inherited MDC, you would get no user name printed in the logs for background tasks, because your thread pool threads would not have anything in the MDC. That's not a good situation, but at least you can spot that there's something missing. OTOH, if you forget to retain the MDC manually with Logback, instead of no data you get false data in the logs. This is because thread pool threads are going to be created with random parent threads. These thread pool threads will then inherit the MDC from these threads, and *keep* the MDC. So future Runnables passed to these threads will print their starting thread's username. False data is worse than no data, so it would be nice to avoid this. Is there a way to make Logback's MDC inheritance configuratble? Like, in logback.xml you could set if you wanted to use InheritableThreadLocals or not. If that doesn't work, it might even be better to have no inheritance at all. What do you think? Regards, Lorant

3 4

logback.groovy or logback.xml class path not recognized in excutable jar
by Rathnadhar.K.V 31 May '11

31 May '11

Namasthe, I want to know how to set the class path context in executable jar so that logback can read the configuration file either logback.groovy or logback.xml. Apparently when we execute the java program out of executable jar, the system set class path is not recognized. Only the classpath set in the MANIFEST file is recognized. Due to this logback (logback.jar) cannot read the user defined configuration hence it falls back to default configuration that only sends the messages to console. I have created the executable jar for my project. I work out of Eclipse environment. In this IDE environment I have set the required class path. When I "run" or "debug" using Eclipse, logback works perfectly. But when I run the executable jar natively (java -jar abc.jar), logback falls back default configuration. Placing the configuration files in the /lib directory where the logback jars are present, does not help. How enable the logback to read the configuration files in executable jar? -- View this message in context: http://old.nabble.com/logback.groovy-or-logback.xml-class-path-not-recogniz… Sent from the Logback User mailing list archive at Nabble.com.

1 0