July 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

Connection leaks with DBAppender and GlassFish?
by Stephan Vollmer-2 08 Aug '11

08 Aug '11

Hi, I use Logback 0.9.29 and the DBAppender to log error messages into a database. The Java EE 6 application runs with GlassFish 3.1 and uses the JNDIConnectionSource to obtain a database connection. I have created a separate database connection pool within GlassFish that is only used for Logback. This pool also has connection leak detection enabled. When the connection leak timeout has passed, the server log has the following error message: [#|2011-07-25T12:18:26.217+0200|INFO|glassfish3.1.1|javax.enterprise.resource.resourceadapter.com.su n.enterprise.resource.pool|_ThreadID=24;_ThreadName=Thread-2;|Reclaiming the leaked connection of pool [ loggerPool ] and destroying it so as to avoid both the application that leaked the connection and any other request that can potentially acquire the same connection from the pool end up using the connection at the same time|#] [#|2011-07-25T12:18:27.841+0200|WARNING|glassfish3.1.1|javax.enterprise.resource.resourceadapter.com .sun.enterprise.resource.pool|_ThreadID=24;_ThreadName=Thread-2;|A potential connection leak detected for connection pool loggerPool. The stack trace of the thread is provided below : com.sun.enterprise.resource.pool.ConnectionPool.setResourceStateToBusy(ConnectionPool.java:324) com.sun.enterprise.resource.pool.ConnectionPool.getResourceFromPool(ConnectionPool.java:758) com.sun.enterprise.resource.pool.ConnectionPool.getUnenlistedResource(ConnectionPool.java:632) com.sun.enterprise.resource.pool.ConnectionPool.internalGetResource(ConnectionPool.java:526) com.sun.enterprise.resource.pool.ConnectionPool.getResource(ConnectionPool.java:381) com.sun.enterprise.resource.pool.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:242) com.sun.enterprise.resource.pool.PoolManagerImpl.getResource(PoolManagerImpl.java:167) com.sun.enterprise.connectors.ConnectionManagerImpl.getResource(ConnectionManagerImpl.java:338) com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:301) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:190) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165) com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:160) com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:113) ch.qos.logback.core.db.JNDIConnectionSource.getConnection(JNDIConnectionSource.java:69) ch.qos.logback.core.db.ConnectionSourceBase.discoverConnnectionProperties(ConnectionSourceBase.java:47) ch.qos.logback.core.db.JNDIConnectionSource.start(JNDIConnectionSource.java:54) ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:167) ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:132) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) ch.qos.logback.classic.selector.ContextJNDISelector.getLoggerContext(ContextJNDISelector.java:108) org.slf4j.impl.StaticLoggerBinder.getLoggerFactory(StaticLoggerBinder.java:108) org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:273) org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) de.mycompany.mb.config.WebServiceConfigurationProvider.<init> (WebServiceConfigurationProvider.java:16) sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) java.lang.reflect.Constructor.newInstance(Constructor.java:513) java.lang.Class.newInstance0(Class.java:355) My logback.xml: <?xml version="1.0" encoding="UTF-8"?> <configuration> <contextName>${project.artifactId}</contextName> <property name="application-name" value="${project.artifactId}" /> <jmxConfigurator /> <appender name="DB" class="ch.qos.logback.classic.db.DBAppender"> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>ERROR</level> </filter> <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource"> </connectionSource> </appender> <root> <level value="DEBUG" /> <appender-ref ref="DB" /> </root> </configuration> The Java code is very simple: public class LogbackTest { private final Logger logger = LoggerFactory.getLogger(LogbackTest.class); @PostConstruct public void init() throws IOException { logger.error("Test error message"); } } Is there probably a problem with my configuration or the way I use Logback? What can I do to avoid the connection leak error messages? I could simply disable connection leak detection, but I don't think that is the right way to deal with it. Thanks in advance for your help! Stephan -- View this message in context: http://old.nabble.com/Connection-leaks-with-DBAppender-and-GlassFish--tp321… Sent from the Logback User mailing list archive at Nabble.com.

2 2

How to log to different files from different classes?
by Mark Kerzner 27 Jul '11

27 Jul '11

Hi, I want to log profiler information to one log, and regular debug information to different one. How would one do that? Thank you, Mark

1 0

Re: [logback-user] Problem with Logback.XML
by BAKHTI Mohammed 25 Jul '11

25 Jul '11

Thanks I have already think about something like this but it's not really nice, (if in the future i need to change smething i have to make changes in java files) No one know about how to "exclude component from the default configuration" or "multi-step configuration" as slf4j doccumentation said ? In slf4j they said : The only way to obtain output from the listed loggers, is to isolate the components invoking these loggers and to exclude them from the default configuration. Both logback and log4j allow multi-step configuration. It follows that the problematic components should be configured in a second step separate from default configuration. To: onlymed(a)hotmail.com; logback-user(a)qos.ch From: djt69(a)comcast.net Subject: Re: [logback-user] Problem with Logback.XML Date: Mon, 4 Jul 2011 11:08:05 -0400 The way I got around it with my filter was to create another class with a static method that the filter called. The other class had a logger instantiated and took care of the logging for the filter. Sent from my Verizon Wireless Phone ----- Reply message ----- From: "BAKHTI Mohammed" <onlymed(a)hotmail.com> Date: Mon, Jul 4, 2011 9:47 am Subject: [logback-user] Problem with Logback.XML To: <djt69(a)comcast.net>, <logback-user(a)qos.ch> Thanks for the replay : so how can i deal with this ? In slf4j they said : The only way to obtain output from the listed loggers, is to isolate the components invoking these loggers and to exclude them from the default configuration. Both logback and log4j allow multi-step configuration. It follows that the problematic components should be configured in a second step separate from default configuration. But i don't figure how ? what really i need to do. Thansk again for any help To: onlymed(a)hotmail.com; logback-user(a)qos.ch From: djt69(a)comcast.net Subject: Re: [logback-user] Problème with Logback.XML Date: Mon, 4 Jul 2011 08:52:24 -0400 If you instantiate a logger in a filter class you'll have the same problem. The message is telling you that you can't use a logger in part of Logback's init. Sent from my Verizon Wireless Phone ----- Reply message ----- From: "BAKHTI Mohammed" <onlymed(a)hotmail.com> Date: Mon, Jul 4, 2011 3:31 am Subject: [logback-user] Problème with Logback.XML To: <logback-user(a)qos.ch> Hello, I just made an API abstraction above logback in order to add specific functions in this api i have all logback functions (juste overrided with no changes) and add some other functions (with specific signature) : I created then a file appender and a JMS appender in logback.xml (nothing special) I am using activemq for jms MOM. The problem is then : when a run a test class with some methodes invocation i see this message : 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: org.apache.activemq.ActiveMQPrefetchPolicy SLF4J: org.apache.activemq.jndi.ReadOnlyContext SLF4J: org.apache.activemq.transport.tcp.TcpTransportFactory SLF4J: org.apache.activemq.util.ServiceSupport All user logs are logged as expected but i dont see any of activemq (or other framework) logs . i have read the information in slf4j url but don't understund what they mean and how to correct this problem in logback . Thanks for any help

2 3

Resource [file:logback.xml] occurs multiple times on the classpath
by Jason Berk 25 Jul '11

25 Jul '11

new user here....making the jump for log4j to logback. Running an executable jar where logback.xml is NOT in the jar. Application works as expected, but I'm seeing all these "Resource [file:logback.xml] occurs at [file:logback.xml]" in the log. jberk@ubuntu:~/apps$ java -Dlogback.configurationFile=file:logback.xml -Dapp.props=file:app.props \ -Dinput.file=test.txt -Doutput.dir=pdf -jar MyJar.jar mortgage 13:01:09,754 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [file:logback.xml] at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs multiple times on the classpath. 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,756 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,757 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:logback.xml] occurs at [file:logback.xml] 13:01:09,830 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 13:01:09,835 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 13:01:09,839 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 13:01:09,866 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property 13:01:09,914 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.springframework] to OFF 13:01:09,914 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache] to OFF 13:01:09,914 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to DEBUG 13:01:09,914 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] ....my app logs omitted..... here is my logback.xml: <?xml version="1.0" encoding="UTF-8"?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d %-5level %C[%M%L] - %msg%n</pattern> </encoder> </appender>  <logger name="org.springframework" level="OFF"/> <logger name="org.apache" level="OFF"/> <root level="debug"> <appender-ref ref="STDOUT"/> </root> </configuration> 1) why is this happening? 2) is this something I am doing wrong (and how to fix) thanks for the great tool and any help. Jason

3 5

ch.qos.logback.access.tomcat.LogbackValve overrides final method start
by Seidler.EDV 24 Jul '11

24 Jul '11

Hello, I tried to configure logback for tomcat 7.0.29 according to the instructions in "HTTP-access logs with logback-access, Jetty and Tomcat". But now I get an exception when I want to start tomcat that states ch.qos.logback.access.tomcat.LogbackValve overrides final method start. Is logback not compatible with tomcat 7? Regards Bernd

1 0