November 2011 - logback-user

tomcat internal logs + logback app logs in one file
by Rohi Fadlun 23 Nov '11

23 Nov '11

Hi, I'm working on a project that needs to have tomcat internal logs and application logs in one file. At the moment I'm using logback to log tomcat internals with grgrzybek's project (https://github.com/grgrzybek/tomcat-slf4j-logback) in which there is a modified version of juli that redirects calls to logback - if I didn't understand wrong) and it works really fine, I just modified a bit its logback configuration so that all 4 loggers refer to only 1 appender; for my application I'm using a simple configuration that outputs to a file, uses a size and time based rolling policy: <configuration scan="true" scanPeriod="30 seconds" > <appender name="MYAPP-TRIAL" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp.log</file> <append>true</append> <encoder> <charset>utf-8</charset> <pattern>MYAPPLICATION TRIAL %d{HH:mm:ss.SSS} %-5level {%thread} [%logger{40}] : %msg%n</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp-%d{yyyyMMdd}-%i.log.zip</fileNamePattern> <maxHistory>60</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>10MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> <root level="info"> <appender-ref ref="MYAPP-TRIAL" /> </root> </configuration> Now I know there are 2 different approaches 1 - using prudent: but i can't use it because of its limitation with the rolling policy (in fact it doesn't work at all with this configuration) 2 - using <include> tag importing the appender from tomcat/conf/logback.xml (I followed logback manual, referencing the appender and so on). This approach doesn't work either, I think because the class used in the tomcat/conf/logback.xml is not logback's classic one: <included> <appender name="MYAPPTEST" class=" org.apache.juli.logging.ch.qos.logback.core.rolling.RollingFileAppender"> <file>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp.log</file> <encoder> <charset>utf-8</charset> <pattern>%d{HH:mm:ss.SSS} %logger{0} {%thread} %level : %msg%n</pattern> </encoder> <rollingPolicy class="org.apache.juli.logging.ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>C:/Users/r0h1/workspace/TestLoggingFrameworks/logs/myapp-%d{yyyyMMdd}-%i.log.zip</fileNamePattern> <maxHistory>60</maxHistory> <timeBasedFileNamingAndTriggeringPolicy class="org.apache.juli.logging.ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>20MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> </included> Someone got another approach to suggest? or am I making something wrong here? I'm using tomcat x64 7.0.22, logback 1.0.0, Win7 x64 Thanks a lot! Rohi

1 0

Groovy-config fails without outside code noticing.
by Endre Stølsvik 18 Nov '11

18 Nov '11

Hi! This groovy-file ...: import ch.qos.logback.classic.PatternLayout import ch.qos.logback.core.ConsoleAppender import ch.qos.logback.core.encoder.LayoutWrappingEncoder appender("STDOUT", ConsoleAppender) { encoder(LayoutWrappingEncoder) { layout(PatternLayout) { pattern = "%d{HH:mm:ss.SSS} [%thread] %-5level %logger{55}.%M.%L - %msg%n" } } } root(ALL, ["STDOUT"]) ... apparently crashes the configuration as such: Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: groovy.lang.MissingPropertyException: No such property: ALL for class: Script1 at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231) at Script1.run(Script1.groovy:13) at Script1$run.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:59) at ch.qos.logback.classic.gaffer.GafferConfigurator$run.callCurrent(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141) at ch.qos.logback.classic.gaffer.GafferConfigurator.run(GafferConfigurator.groovy:37) at ch.qos.logback.classic.gaffer.GafferUtil.runGafferConfiguratorOn(GafferUtil.java:44) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:67) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) 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:128) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:108) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:279) at XYZ.doLogConfig(XYZ.java:40) at XYZ.main(XYZ:169) * The problem is obviously the not-defined property "ALL". The problem I am reporting is that this isn't caught.* The console-dump happens in the *"We should never get here"* catch block below: void init() { try { try { new ContextInitializer(defaultLoggerContext).autoConfig(); } catch (JoranException je) { Util.report("Failed to auto configure default logger context", je); } StatusPrinter.printInCaseOfErrorsOrWarnings(defaultLoggerContext); contextSelectorBinder.init(defaultLoggerContext, KEY); initialized = true; } catch (Throwable t) { // we should never get here Util.report("Failed to instantiate [" + LoggerContext.class.getName() + "]", t); } } Notice that the StatusManager does not know that the config failed: 13:32:07,643 |-INFO in ch.qos.logback.classic.LoggerContext[Emma logcontext] - Found resource [logback.groovy] at [file:/XYZ/target/classes/logback.groovy] 13:32:08,807 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2111e072 - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 13:32:08,809 |-INFO in ch.qos.logback.classic.gaffer.ConfigurationDelegate@2111e072 - Naming appender as [STDOUT] Kind regards, Endre Stølsvik.

2 1

Joran errors I don't understand
by Steve Cohen 17 Nov '11

17 Nov '11

We have this configuration <configuration> ... <conversionRule conversionWord="ourcaller" converterClass="com.whatever.CallerDataConverter" /> <appender name="jms" class="com.whatever.JMSQueueAppender"> <encoder> <pattern>%d %-5p [%t] %ourcaller{1} - %m%n</pattern> </encoder> </appender> <appender name="stdout" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%d %-5p [%t] %ourcaller{1} %n - %m%n</pattern> </encoder> </appender> ... ====================================== This configuration produces these errors: 3:21:43,935 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@18:14 - no applicable action for [encoder], current pattern is [[configuration][appender][encoder]] 13:21:43,935 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@19:16 - no applicable action for [pattern], current pattern is [[configuration][appender][encoder][pattern]] The line numbers here refer to the JMSQueueAppender. The console appender which is structured basically identically has no such problem. What is Joran trying to tell me here. It appears to be telling me the pattern I am using, but does not tell me why it finds this objectionable. Thanks.

2 4

How to log FROM an appender?
by Steve Cohen 16 Nov '11

16 Nov '11

We have a custom appender that may itself need to issue logging statements. But placing a logger in such a class causes various exceptions on initialization and loading. So we are resorting to System.out.println for lack of a better solution. I suppose there must be a better way. What would that be?

4 16

Re: [logback-user] Logback-user Digest, Vol 2, Issue 32
by Yuvaraj Vanarase 16 Nov '11

16 Nov '11

Hello Ceki, It would be great if you provide confirmation for your answer below: There is a serious bug in AccessViewStatus servlet. That is probably why you are seeing the 'Could not find status manager' message which will be fixed with the logback next release. Does this also cause the logback-access initialization logs to be absent on console? I mean I wouldn't able to see something like: 21:56:09,921 |-INFO in c.q.lb.access.j.a.ConfigurationAction - Ignoring debug attribute. 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 21:56:09,921 |-INFO in c.q.lb.core.j.a.AppenderAction - Naming appender as [STDOUT] 21:56:10,000 |-INFO in c.q.lb.core.j.a.NestedComponentIA - Pushing component [layout] on top of the object stack. 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderAction - Popping appender named [STDOUT] from the object stack 21:56:10,015 |-INFO in c.q.lb.core.j.a.AppenderRefAction - Attaching appender named [STDOUT] to ch.qos.logback.access.tomcat.LogbackValve[Catalina] 21:56:10,015 |-INFO in c.q.lb.access.j.a.ConfigurationAction - End of configuration. Because apart from status manager issue, I do not see above initialization log either. Regards, Yuvaraj Date: Wed, 16 Nov 2011 08:02:14 +0100 From: Ceki Gulcu <ceki(a)qos.ch> To: logback users list <logback-user(a)qos.ch> Subject: Re: [logback-user] Using logback access Message-ID: <4EC35FF6.10907(a)qos.ch> Content-Type: text/plain; charset=windows-1252; format=flowed Hello Yuvaraj, Responses inline. On 16.11.2011 07:05, Yuvaraj Vanarase wrote: > Hi, > > I have 2 questions. > > 1. What is logback access exactly. Is it about providing webserver > request information in terms of log. Doesn?t such facility come with web > server itself? (catalina.log for tomcat etc) Yes, web-containers already support access logging. Logback-access provides the same functionality but in addition logback-access is more flexible with much better filtering and rolling capabilities. > 2. I am trying to use logback access with Tomcat, however just not > getting there. It would be great if someone points out any miss-outs. > > Below are details: > > -Tomcat 6.0.33 > > -Logback core 0.9.30 > > -Logback access 0.9.30 > > I have put above logback jars into tomcat jar directory. I have added > ?Valve? configuration in server.xml and as required put the > logback-access.xml in conf directory of tomcat. I referred > http://logback.qos.ch/access.html > > My webapp has single simple servlet that just prints login name on page > which has been input from html login form. This works well however I do > not see any logback initialization logs. When I query > ?AccessViewStatusMessages?, again I do not see any messages except one > *?Could not find status manager?* There is a serious bug in AccessViewStatus servlet. That is probably why you are seeing the 'Could not find status manager' message which will be fixed with the logback next release. > Yuvaraj ------------------------------ _______________________________________________ Logback-user mailing list Logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user End of Logback-user Digest, Vol 2, Issue 32 *******************************************

2 1

Using logback access
by Yuvaraj Vanarase 16 Nov '11

16 Nov '11

Hi, I have 2 questions. 1. What is logback access exactly. Is it about providing webserver request information in terms of log. Doesn't such facility come with web server itself? (catalina.log for tomcat etc) 2. I am trying to use logback access with Tomcat, however just not getting there. It would be great if someone points out any miss-outs. Below are details: -Tomcat 6.0.33 -Logback core 0.9.30 -Logback access 0.9.30 I have put above logback jars into tomcat jar directory. I have added 'Valve' configuration in server.xml and as required put the logback-access.xml in conf directory of tomcat. I referred http://logback.qos.ch/access.html My webapp has single simple servlet that just prints login name on page which has been input from html login form. This works well however I do not see any logback initialization logs. When I query 'AccessViewStatusMessages', again I do not see any messages except one 'Could not find status manager' Here is logback-access.xml content: <configuration debug="true">  <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%h %l %u %user %date "%r" %s %b</pattern> </encoder> </appender> <appender-ref ref="STDOUT" /> </configuration> Regards, Yuvaraj Yuvaraj Vanarase, Lead Technology - Software Phone: +91.20.40262000 Ext 2305|Mobile: +91.9850818870 | http://www.synechron.com SYNECHRON - - Top 15 Best IT Employers for 5 consecutive years (link<http://www.synechron.com/news/news_best_employer_sep2011.htm>). - Celebrating 10 Years!

2 1

Configuration in code only
by Yair Ogen 14 Nov '11

14 Nov '11

Hi, I am a part of an infrastructure team in my company. I have a requirement where I need to support logback configured from code only (infrastructure code). I cannot have users define a logback config file in their respective modules. The goal is to have an infrastructure module that reads configuration from a property file (not log4j.properties). This file is the placeholder for all the application real configuration. We defined a "language" in which users can instruct the infrastructure on how to configure logback. E.g.: logger.com.mycompany.1.appender.name=rollingFile logger.com.mycompany.1.appender.layout=%m%n My code parses these properties and needs to configure logback accordingly. My question is - how do I configure logback in code (assuming the main class is managed by application teams and not infra). I need to wrap a concise logback config file inside the infra module (jar) that holds just enough to give me the code "window" in which I can start the parsing mentioned above. Any ideas? Thanks, Yair

1 0

Janino not found after logback 0.9.27
by Joel Uckelman 13 Nov '11

13 Nov '11

I have this in my logback.xml: <configuration> <contextName>${VASSAL.id:-0}</contextName> <appender name="FILE" class="ch.qos.logback.core.FileAppender"> <if condition='property("os.name").toLowerCase().startsWith("windows")'> <then> <file>${user.home}/VASSAL/errorLog</file> </then> <else> <file>${user.home}/.VASSAL/errorLog</file> </else> </if> <encoder> <pattern>%date [%contextName-%thread] %-5level %logger - %msg%n</pattern> </encoder> <prudent>true</prudent> </appender> <root level="ALL"> <appender-ref ref="FILE" /> </root> </configuration> It works properly with logback 0.9.27 and earlier. With every version after 0.9.27, I get the following output to stderr and no logfile is written: 22:07:09,571 |-INFO in ch.qos.logback.classic.LoggerContext[0] - Could NOT find resource [logback.groovy] 22:07:09,572 |-INFO in ch.qos.logback.classic.LoggerContext[0] - Could NOT find resource [logback-test.xml] 22:07:09,572 |-INFO in ch.qos.logback.classic.LoggerContext[0] - Found resource [logback.xml] at [jar:file:/home/uckelman/projects/VASSAL/VASSAL-src/lib/Vengine.jar!/logback.xml] 22:07:09,590 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@7f2ad19e - URL [jar:file:/home/uckelman/projects/VASSAL/VASSAL-src/lib/Vengine.jar!/logback.xml] is not of type file 22:07:09,784 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 22:07:09,800 |-INFO in ch.qos.logback.classic.joran.action.ContextNameAction - Setting logger context name as [0] 22:07:09,800 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.FileAppender] 22:07:09,803 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 22:07:09,805 |-ERROR in ch.qos.logback.core.joran.conditional.IfAction - Could not find Janino library on the class path. Skipping conditional processing. 22:07:09,824 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@16:14 - no applicable action for [encoder], current pattern is [[configuration][appender][encoder]] 22:07:09,824 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@17:16 - no applicable action for [pattern], current pattern is [[configuration][appender][encoder][pattern]] 22:07:09,825 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@19:14 - no applicable action for [prudent], current pattern is [[configuration][appender][prudent]] 22:07:09,825 |-ERROR in ch.qos.logback.core.FileAppender[FILE] - "File" property not set for appender named [FILE]. 22:07:09,825 |-WARN in ch.qos.logback.core.joran.action.AppenderAction - The object at the of the stack is not the appender named [FILE] pushed earlier. 22:07:09,825 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to ALL 22:07:09,825 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT] 22:07:09,828 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@54281d4b - Registering current configuration as safe fallback point Specifically, I'm concerned about the the first error, which claims that Janino can't be found in the classpath, because I'm certain that janino.jar is in the classpath (and logback 0.9.27 seems to find it). What changed in 0.9.28 that's causing this? Is it something that I need to adjust in my own code, or is this a bug in logback? -- J.

2 5

Missing documentation
by Steve Cohen 13 Nov '11

13 Nov '11

Javadocs at http://logback.qos.ch/apidocs/index.html?ch/qos/logback/core/net/package-su… as well as http://logback.qos.ch/apidocs/ch/qos/logback/classic/net/JMSQueueAppender.h… refers (under the heading JMSAppenderBase<E>) as follows: > please refer to: http://logback.qos.ch/manual/appenders.html#JMSAppenderBase > please refer to: http://logback.qos.ch/manual/appenders.html#JMSQueueAppender However, no such anchors exist on this manual page and the extra information appears to be unavailable.

1 0

Compression in SiftingAppender
by TJ Rothwell 11 Nov '11

11 Nov '11

Hi, I'm using SiftingAppender on top of an appender that uses compression. When using a variable (like username) that will show up more than once, it works great. But when using a session id which is unique, then the log file will not be triggered for compression leading to larger disk usage. Is there a way to go about triggering the file to be compressed when the SiftingAppender closes the child appender after it's timeout period? Definition of my appender: <appender name="SIFT-SESSION_ID" class="ch.qos.logback.classic.sift.SiftingAppender"> <discriminator class="ch.qos.logback.classic.sift.MDCBasedDiscriminator"> <key>SESSION_ID</key> <defaultValue>unknown</defaultValue> </discriminator> <sift> <appender name="FILE-${SESSION_ID}" class="ch.qos.logback.core.rolling.RollingFileAppender"> <encoder> <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS zz} %-5level [%thread] %logger{35} - %msg%n%xEx{full}</pattern> </encoder> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>${CONTEXT_DATA_PATH}/logs/session/session-${SESSION_ID}.%d{yyyy-MM-dd}.%i.txt.zip</fileNamePattern> <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP"> <maxFileSize>100MB</maxFileSize> </timeBasedFileNamingAndTriggeringPolicy> </rollingPolicy> </appender> </sift> </appender> Thanks! -- TJ

2 17