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

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

Are included files scanned
by Rosarin Jolly Roy 12 Feb '11

12 Feb '11

I have a top-level config file logback.xml and another file logback-included.xml. If I set the scan=true in the logback.xml file, will the included file also be scanned for changes? Is scan=true applicable for <included> tag as well? I find that the scanning doesn't happen, when I change the included file. Should I do anything special? --- logback.xml --- <configuration scan="true"> <include file="logback-included.xml" /> </configuration> --- logback-included.xml --- <included scan="true"> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>mylog.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <FileNamePattern>mylog.log.%d{yyyy-MM-dd}</FileNamePattern> </rollingPolicy> <encoder> <pattern>%date %level [%thread] %logger{15} %msg%n</pattern> </encoder> </appender> <root> <level value="DEBUG" /> <appender-ref ref="FILE" /> </root> </included> _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:…

4 7

Logback and Facebook Scribe
by BenT 21 Jan '11

21 Jan '11

Hi, Out of curiosity, has anybody used Facebook's scribe interface as a logging destination for logback? Thanks in advance, Ben -- View this message in context: http://old.nabble.com/Logback-and-Facebook-Scribe-tp28539373p28539373.html Sent from the Logback User mailing list archive at Nabble.com.

2 1

Appender Ref Default Value
by David Harrigan 02 Jul '10

02 Jul '10

Hiya, I love the fact that in logback I can do this for a level: <logger name="foo" level="${foo.bar.log.level:-debug}"/> I would love to be able to do the following as well: <appender-ref ref="${foo.bar.log.appender:-console}"/> So that I can switch between different appenders during build time. At the moment, If I try that, I get this warning from logback (0.9.21) 11:17:32,676 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - Could not find an appender named [${foo.bar.log.appender:-console}]. Did you define it below in the config file? 11:17:32,676 |-ERROR in ch.qos.logback.core.joran.action.AppenderRefAction - See http://logback.qos.ch/codes.html#appender_order for more details. Is this achievable? -=david=- -- View this message in context: http://old.nabble.com/Appender-Ref-Default-Value-tp28605941p28605941.html Sent from the Logback User mailing list archive at Nabble.com.

2 5

Google App Engine and java.net.InetAddress
by cosanta 28 May '10

28 May '10

I'm trying to hook up slf4j/logback into a Google App Engine project but it looks like I'm running into a problem with a class that GAE blocks, namely java.net.InetAddress. I'm using the latest: slf4j 1.6.0 and logback 0.9.21, tied into v1.3.3.1 of the AppEngine SDK and here is my java version: * java version "1.6.0_18" * OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1) * OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) If I don't include a logback.xml, my gae dev server starts up properly and I see my log messages printed to the console. The place in *my* code where the failure happens is in the very first call to grab the logger, in com.cosanta.eventflow.control.EventServletContextListener:43, which is just: private org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(this.getClass().getName()); I took the logback.xml right out of the examples: logback-examples/src/main/java/chapters/configuration/sample0.xml: <?xml version="1.0" encoding="UTF-8" ?> <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <root level="debug"> <appender-ref ref="STDOUT" /> </root> </configuration> When I try to start the GAE dev server from my eclipse workspace, I get the following printed to the console: May 21, 2010 1:25:05 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml INFO: Successfully processed /home/sean/Dropbox/dev/workspace/EventFlow/war/WEB-INF/web.xml Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.NoClassDefFoundError: java.net.InetAddress is a restricted class. Please see the Google App Engine developer's guide for more details. at com.google.appengine.tools.development.agent.runtime.Runtime.reject(Runtime.java:51) at ch.qos.logback.core.util.ContextUtil.addHostNameAsProperty(ContextUtil.java:34) at ch.qos.logback.classic.joran.action.ConfigurationAction.begin(ConfigurationAction.java:47) at ch.qos.logback.core.joran.spi.Interpreter.callBeginAction(Interpreter.java:273) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:145) at ch.qos.logback.core.joran.spi.Interpreter.startElement(Interpreter.java:127) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:40) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:60) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:121) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at com.cosanta.eventflow.control.EventServletContextListener.<init>(EventServletContextListener.java:43) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at org.mortbay.jetty.webapp.WebXmlConfiguration.newListenerInstance(WebXmlConfiguration.java:650) at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(WebXmlConfiguration.java:631) at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:368) at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at org.mortbay.jetty.Server.doStart(Server.java:224) at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at com.google.appengine.tools.development.JettyContainerService.startContainer(JettyContainerService.java:185) at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java:146) at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:219) at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:162) at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48) at com.google.appengine.tools.development.DevAppServerMain.<init>(DevAppServerMain.java:113) at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89) 01:25:06,971 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [WEB-INF/logback.xml] at [file:/home/sean/Dropbox/dev/workspace/EventFlow/war/WEB-INF/logback.xml] 01:25:07,598 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set The server is running at http://localhost:8888/ So as you can see, the server starts fine. It has no problem handling requests etc but there is no further logging displayed. The logback code that causes GAE to scream is the placement of the hostname onto the context in ContextUtils:34: InetAddress localhost = InetAddress.getLocalHost(); context.putProperty(CoreConstants.HOSTNAME_KEY, localhost.getHostName()); Has anyone seen the same problem? Is there something I'm misconfiguring? If not, is there any way to work around this? Thanks for your help. Sean -- View this message in context: http://old.nabble.com/Google-App-Engine-and-java.net.InetAddress-tp28628992… Sent from the Logback User mailing list archive at Nabble.com.

1 0

Re: [logback-user] Logback and tomcat
by cosanta 28 May '10

28 May '10

Daniel, I was running into what looks like a similar problem. I'm trying to integrate slf4j/logback into a google app engine project. Console logging works fine when I don't create my own logback.xml. I was using SLF4J 1.5.11 with logback 0.9.19 when I ran across your post. I upgraded to slf4j 1.6.0 and logback 0.9.21 and those specific problems disappeared. Still working on some others though... -- Sean Daniel Proud wrote: > > Hi guys, > > I am attempting to get logback working with my tomcat webapp and have > run into a few issues. > > I have got various log messages in my client code and they seem to work > when run seperate from the web app (eg junit testing in eclipse uses the > default configuration and the log messages appear in the console.) > > When I run this code embedded in a webapp on my local tomcat5.5 install > (from within eclipse again) I can see logback internal messages in the > eclipse console view: > > 23/04/2010 10:15:19 AM org.apache.catalina.core.AprLifecycleListener > lifecycleEvent > INFO: The Apache Tomcat Native library which allows optimal performance > in production environments was not found on the java.library.path: > C:\Program > Files\Java\jdk1.6.0_16\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program > Files (x86)\CollabNet Subversion > Client;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program > Files (x86)\ATI Technologies\ATI.ACE\Core-Static;c:\Program Files > (x86)\Microsoft SQL > Server\90\Tools\binn\;C:\msys\1.0\bin;C:\mingw\bin;C:\cygwin\bin;C:\Program > Files (x86)\TortoiseHg;C:\Program Files (x86)\Mercurial\;C:\Program > Files (x86)\CVSNT\ > 23/04/2010 10:15:19 AM org.apache.coyote.http11.Http11BaseProtocol init > INFO: Initializing Coyote HTTP/1.1 on http-8080 > 23/04/2010 10:15:19 AM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 484 ms > 23/04/2010 10:15:20 AM org.apache.catalina.core.StandardService start > INFO: Starting service Catalina > 23/04/2010 10:15:20 AM org.apache.catalina.core.StandardEngine start > INFO: Starting Servlet Engine: Apache Tomcat/5.5.28 > 23/04/2010 10:15:20 AM org.apache.catalina.core.StandardHost start > INFO: XML validation disabled > 23/04/2010 10:15:20 AM org.apache.catalina.loader.WebappClassLoader > validateJarFile > INFO: > validateJarFile(E:\workspaces\default\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\wtpwebapps\web-keno\WEB-INF\lib\servlet-api-2.4.jar) > - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: > javax/servlet/Servlet.class > 10:15:20,578 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > Could NOT find resource [logback-test.xml] > 10:15:20,578 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > Found resource [logback.xml] at > [file:/E:/workspaces/default/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/web-keno/WEB-INF/classes/logback.xml] > 10:15:20,625 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > About to instantiate appender of type > [ch.qos.logback.core.rolling.RollingFileAppender] > 10:15:20,625 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > Naming appender as [FILE] > 10:15:20,656 |-INFO in > ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing > component [rollingPolicy] on top of the object stack. > 10:15:20,671 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No > compression will be used > 10:15:20,671 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will > use the pattern E:/apache-tomcat-5.5.28/logs/keno.%d{yyyy-MM-dd}.log for > the active file > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy@755c62bc > - The date pattern is 'yyyy-MM-dd' from file name pattern > 'E:/apache-tomcat-5.5.28/logs/keno.%d{yyyy-MM-dd}.log'. > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy@755c62bc > - Roll-over at midnight. > 10:15:20,687 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@10:12 > - no applicable action for [encoder], current pattern is > [[configuration][appender][encoder]] > 10:15:20,687 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@11:13 > - no applicable action for [pattern], current pattern is > [[configuration][appender][encoder][pattern]] > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file > name: E:/apache-tomcat-5.5.28/logs/keno.2010-04-23.log > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is > set to [null] > 10:15:20,687 |-ERROR in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - No layout set > for the appender named "FILE". > 10:15:20,687 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > Popping appender named [FILE] from the object stack > 10:15:20,687 |-INFO in > ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of > ROOT logger to ALL > 10:15:20,687 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender > named [FILE] to Logger[ROOT] > 10:15:20,687 |-INFO in > ch.qos.logback.classic.joran.action.ConfigurationAction - End of > configuration. > > 10:15:20,578 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > Could NOT find resource [logback-test.xml] > 10:15:20,578 |-INFO in ch.qos.logback.classic.LoggerContext[default] - > Found resource [logback.xml] at > [file:/E:/workspaces/default/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/web-keno/WEB-INF/classes/logback.xml] > 10:15:20,625 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > About to instantiate appender of type > [ch.qos.logback.core.rolling.RollingFileAppender] > 10:15:20,625 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > Naming appender as [FILE] > 10:15:20,656 |-INFO in > ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Pushing > component [rollingPolicy] on top of the object stack. > 10:15:20,671 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - No > compression will be used > 10:15:20,671 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will > use the pattern E:/apache-tomcat-5.5.28/logs/keno.%d{yyyy-MM-dd}.log for > the active file > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy@755c62bc > - The date pattern is 'yyyy-MM-dd' from file name pattern > 'E:/apache-tomcat-5.5.28/logs/keno.%d{yyyy-MM-dd}.log'. > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy@755c62bc > - Roll-over at midnight. > 10:15:20,687 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@10:12 > - no applicable action for [encoder], current pattern is > [[configuration][appender][encoder]] > 10:15:20,687 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@11:13 > - no applicable action for [pattern], current pattern is > [[configuration][appender][encoder][pattern]] > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file > name: E:/apache-tomcat-5.5.28/logs/keno.2010-04-23.log > 10:15:20,687 |-INFO in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is > set to [null] > 10:15:20,687 |-ERROR in > ch.qos.logback.core.rolling.RollingFileAppender[FILE] - No layout set > for the appender named "FILE". > 10:15:20,687 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - > Popping appender named [FILE] from the object stack > 10:15:20,687 |-INFO in > ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of > ROOT logger to ALL > 10:15:20,687 |-INFO in > ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender > named [FILE] to Logger[ROOT] > 10:15:20,687 |-INFO in > ch.qos.logback.classic.joran.action.ConfigurationAction - End of > configuration. > > 23/04/2010 10:15:20 AM org.apache.axis.utils.JavaUtils > isAttachmentSupported > WARNING: Unable to find required classes (javax.activation.DataHandler > and javax.mail.internet.MimeMultipart). Attachment support is disabled. > 23/04/2010 10:15:21 AM org.apache.coyote.http11.Http11BaseProtocol start > INFO: Starting Coyote HTTP/1.1 on http-8080 > 23/04/2010 10:15:21 AM org.apache.jk.common.ChannelSocket init > INFO: JK: ajp13 listening on /0.0.0.0:8009 > 23/04/2010 10:15:21 AM org.apache.jk.server.JkMain start > INFO: Jk running ID=0 time=0/47 config=null > 23/04/2010 10:15:21 AM org.apache.catalina.storeconfig.StoreLoader load > INFO: Find registry server-registry.xml at classpath resource > 23/04/2010 10:15:21 AM org.apache.catalina.startup.Catalina start > INFO: Server startup in 1375 ms > > The config does not appear twice when I turn off the debug option in the > below logback.xml: > > <?xml version="1.0" encoding="UTF-8"?> > <configuration debug="true"> > <appender name="FILE" > class="ch.qos.logback.core.rolling.RollingFileAppender"> > <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> > <FileNamePattern>${catalina.home}/logs/keno.%d{yyyy-MM-dd}.log</FileNamePattern> > <MaxHistory>30</MaxHistory> > </rollingPolicy> > > <encoder> > <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - > %msg%n</pattern> > </encoder> > </appender> > > <root level="all"> > <appender-ref ref="FILE" /> > </root> > </configuration> > > However nothing seems to get logged. It creates the log file however it > remains at 0 bytes. I tried using a console appender and had the same > problem - the log messages did not appear on the console. > > When I try to run the above app on a ubuntu9/tomcat6 production-like > environment, I get the same issue (no log messages) except I can't find > the console output at all. I have a feeling that is a tomcat config > issue though - I can't find catalina.out anywhere. > > Any ideas what might be causing the log messages to disappear? > > Cheers, > Dan > -- > *Daniel Proud* > Analyst Programmer > ------------------------------------------------------------------------ > Tel: (02) 6245 6267 > Fax: (02) 6245 6242 > Mob: 0417 291 323 > Email: danielp(a)acttab.com.au <mailto:danielp@acttab.com.au> > Web: http://www.acttab.com.au > > ACTTAB <http://www.acttab.com.au> > > ------------------------------------------------------------------------ > > The information transmitted is intended only for the person to whom it > is addressed and may contain confidential and/or privileged material. > Any review, retransmission, interference with, copying or other use of, > or taking of any action in reliance on this information by persons other > than the intended recipient is prohibited. If you have received this > information in error, please contact the sender immediately and delete > the material from your computer. It is the recipient’s responsibility to > check this message and any attachments for viruses. > > _______________________________________________ > Logback-user mailing list > Logback-user(a)qos.ch > http://qos.ch/mailman/listinfo/logback-user > > -- View this message in context: http://old.nabble.com/Logback-and-tomcat-tp28336217p28628266.html Sent from the Logback User mailing list archive at Nabble.com.

1 0

Collisions between primary and included configuration files
by Becker, Thomas 28 May '10

28 May '10

Our main logback.xml file is jarred up with our application. We'd like to be able to have an "override file" in which we could simply specify the settings we wanted to be different than the main file. I thought about using the file inclusion feature to include the override file from the main config, but the manual doesn't describe the behavior when the included file and the primary file have conflicting settings (for example a logger level). Any ideas on how to accomplish this? Thanks!

2 3

MaxHistory does not delete old files
by viral 28 May '10

28 May '10

Hello. This was reported in previous versions on logback that MaxHistory does not delete old files. This bug is still present in 0.9.21. I tried numerous of configs and nothing. example : <appender name="STD" class="ch.qos.logback.core.rolling.RollingFileAppender"> <Append>true</Append> <File>${log.dir}/log.log</File> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date{HH:mm:ss} %msg%n</pattern> </layout> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${log.arch.dir}/log%d{yyyy-MM-dd}.log</fileNamePattern> <MaxHistory>5</MaxHistory> </rollingPolicy> </appender> I have also tried : <TimeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <MaxHistory>5</MaxHistory> </TimeBasedFileNamingAndTriggeringPolicy> And still old files were not deleted. Can anyone advice ? I do smth wrong ? Being desperate I will delete all those files in my java code. greets Tomasz

2 2

No message when if config file present
by Joel Rosi-Schwartz 27 May '10

27 May '10

Hi, I have a bit of strange problem that I do not understand at all. I am working on sorting out a bit of a nightmare at work. We have 100s of project that get mixed in various way into applications packaged in war's and ear's. There are a number of logging technologies uses through these projects including logback, log4j, slf4j and JCL. (It's a goodness I have not found JUL yet:) On of the issues I am working on is to reduce the noise from third party libraries. I tracked down some of this to JCL being used and eventually logback getting control of the output. As a quick fix while I sort a proper strategy I decided to add a logback.xml configuration to one of the applications. Sure enough all of the debug noise from the third party libraries subsided. As I next step I tried to turn the debug back on and oddly I cannot. If I rename logback.xml the debug message start again. This seems so straightforward I cannot imagine what I am doing wrong. The two version of the configuration file follow. === INFO Level <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> </root> </configuration> === DEBUG Level <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </pattern> </encoder> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> </root> </configuration> Any ideas of where I am going wrong would be very appreciated. Many thanks, Joel

2 3

Conditional RollingFileAppender or Sifter?
by Sean Crotty 21 May '10

21 May '10

Can I configure a RollingAppender/Sifter to NOT keep a file if a certain condition is not met? For example, I don't want to save rolled files that don't have at least one logged statement of WARN level or higher. Here is my use case: have a sifter that creates multiple files - one per transaction. There are thousands of transactions in my system. I only want a transaction log file saved if there is something interesting about that particular transaction. For me, "interesting" is a WARN or ERROR statement in the log file. I don't know if this would be part of the RollingFileAppender or maybe something done when the sifter times out. Any advice? Thanks! Sean

1 0