December 2006 - logback-dev

[Bug 8] New: The insertion of a percent symbol causes the Parser to crash
by bugzilla-daemon＠pixie.qos.ch 19 Mar '08

19 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=8 Summary: The insertion of a percent symbol causes the Parser to crash Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Pattern AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch When inserting the percent char twice, so that it appears in the PatternLayout output, a number format exception is thrown. It does not prevent from using normally the PatternLayout. trace: ERROR in ch.qos.logback.core.joran.spi.Interpreter@131f71a - Exception in Action for tag <layout>8:14 java.lang.NumberFormatException: For input string: "% %" java.lang.NumberFormatException: For input string: "% %" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:447) at java.lang.Integer.parseInt(Integer.java:497) at ch.qos.logback.core.pattern.FormatInfo.valueOf(FormatInfo.java:70) at ch.qos.logback.core.pattern.parser.Parser.T(Parser.java:84) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:51) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.parse(Parser.java:31) at ch.qos.logback.core.pattern.PatternLayoutBase.start(PatternLayoutBase.java:76) at ch.qos.logback.core.joran.action.AbstractLayoutAction.end(AbstractLayoutAction.java:75) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:289) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:152) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:125) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:101) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:84) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:77) at mainPackage.ConfigTester.main(ConfigTester.java:21) -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 5

[ANN] Release of logback 0.7.1
by Sebastien Pennec 23 Jan '07

23 Jan '07

December 19th, 2006 - Release of version 0.7 Version 0.7.1 of logback has been released. This version contains more detailled information about logback access module, and its JMX components. A dedicated page[1] explains how to configure and use logback access in Tomcat and Jetty, and access some of its components via JMX. Links: [1] http://logback.qos.ch/access.html -- Sébastien Pennec sebastien(a)qos.ch Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch/

1 1

[Bug 30] New: What do we do with the logback-demo project?
by bugzilla-daemon＠pixie.qos.ch 23 Jan '07

23 Jan '07

http://bugzilla.qos.ch/show_bug.cgi?id=30 Summary: What do we do with the logback-demo project? Product: logback-general Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: build-structure AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch The logback-demo should be presented to the outside world. Do we add it to the logback structure as another sub project of logback-parent? Do we make an additionnal level of parent pom.xml files that would group logback components, demos, and skin+site? Possible problem: building the assembly might be an issue if all the sub modules are not presents. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 19] New: In there is an error in the expession, JaninoEventEvaluatorBase throws an excpetion
by bugzilla-daemon＠pixie.qos.ch 23 Jan '07

23 Jan '07

http://bugzilla.qos.ch/show_bug.cgi?id=19 Summary: In there is an error in the expession, JaninoEventEvaluatorBase throws an excpetion Product: logback-classic Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: blocker Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: ceki(a)qos.ch If there is an error in the expression passed to JaninoEventEvaluator, then the JaninoEE will throw an excpetion, sometimes an NPE to higher levels. Loggers do not seem to catch the NPE, nor does EvaluatorFilter. Here is a stack trace: Exception in thread "main" java.lang.NullPointerException at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.evaluate(JaninoEventEvaluatorBase.java:58) at ch.qos.logback.core.filter.EvaluatorFilter.decide(EvaluatorFilter.java:48) at ch.qos.logback.core.spi.FilterAttachableImpl.getFilterChainDecision(FilterAttachableImpl.java:68) at ch.qos.logback.core.AppenderBase.getFilterChainDecision(AppenderBase.java:115) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:65) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:286) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:270) at ch.qos.logback.classic.Logger.filterAndLog(Logger.java:375) at ch.qos.logback.classic.Logger.debug(Logger.java:398) at chapter5.GoMDC.main(GoMDC.java:28) The expresison is: <Expression>message.conts("I know me 1")</Expression> -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 3

[Bug 9] New: PostContentConverter
by bugzilla-daemon＠pixie.qos.ch 23 Jan '07

23 Jan '07

http://bugzilla.qos.ch/show_bug.cgi?id=9 Summary: PostContentConverter Product: logback-access Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch At the moment, the PostContentConverter consumes the bytes present in the request's InputStream and returns them as a String. It seems that it is quite a dangerous behaviour, since several sources consider the inputStream as a read-once component. This converter has been removed from access' PatternLayout. We should create a real-life webservice and soap requests, then test the PostContentConverter against the webservice. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 32] New: Default configuration is not disabled when doing explicit configuration
by bugzilla-daemon＠pixie.qos.ch 23 Jan '07

23 Jan '07

http://bugzilla.qos.ch/show_bug.cgi?id=32 Summary: Default configuration is not disabled when doing explicit configuration Product: logback-general Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: major Priority: P1 Component: build-structure AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.ceki(a)qos.ch Many logback examples shipping with the 0.7.1. distribution explicitly configure logback. However, since default configuration invokes BasicConfigurator in the absence of the default logback.xml file, there is an extra console appender configuration. We need to check the code so that we reset the config when we explicitly configure logback. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

[Bug 22] New: Default config conflicting with examples
by bugzilla-daemon＠pixie.qos.ch 12 Jan '07

12 Jan '07

http://bugzilla.qos.ch/show_bug.cgi?id=22 Summary: Default config conflicting with examples Product: logback-classic Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch The new default config behaviour prevents the use of a class with a main method that takes the path to a config file as a first parameter. Either the logback-test.xml, or the BasicConfigurator, seem to take the lead. When using the example classes, there are two output: the one specified in the config file passed as a parameter _and_ the one coming from logback-test or BasicConfigurator. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 5

svn commit: r1149 - in logback/trunk/logback-site/src/site/xdocTemplates: . manual
by noreply.seb＠qos.ch 22 Dec '06

22 Dec '06

Author: seb Date: Fri Dec 22 20:39:40 2006 New Revision: 1149 Added: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml Log: on going work Added: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Fri Dec 22 20:39:40 2006 @@ -0,0 +1,105 @@ +<?xml version="1.0"?> +<document> + + <properties> + <author email="ceki at qos ddoott ch ">Ceki Gulcu</author> + <author email="sebastien at qos ddoott ch ">Sebastien Pennec</author> + <title>Logback Demo</title> + </properties> + + <body> + +<h2>Logback Demo</h2> + + + Welcome to the logback demo! This document will take you to a tour + that will show you some of the most useful possibilities of logback. + + + + First, please download the logback demo. You will need a + <a href="http://subversion.tigris.org/">Subversion</a> client + and issue the following command: + + +<div class="source"><pre>svn co https://svn.qos.ch/repos/logback-demo logback-demo</pre></div> + + + This will checkout a copy of the logback demonstration web-app to a directory called + logback-demo. The logback demo can be packaged as a war file and + deployed to an application server. We strongly recommand the use of + <a href="http://maven.apache.org/">Maven 2</a> to do this + task, since all it will take to compile, package and run a server with the demo is + a single command. + + + + Using Maven, let's run the demo for the first time. From the logback-demo + directory, issue the following command: + + +<div class="source"><pre>mvn jetty:run</pre></div> + + + Then, visit http://localhost:8080/ to view the main page of the logback demo. + + +image main page + + + For now, logback uses two components: one <code>ConsoleAppender</code> and one + <code>RollingFileAppender</code>. The <code>RollingFileAppender</code> sends logging events + to a file called logFile.log and will rollover + the active file every minute. The old file will be renamed and compressed using the zip + format. The <code>ConsoleAppender</code> will output the logging requests to the console, + and shorten the logger names to gain some space in the console window, without making the + names unreadable. + + + + Let's now visit the ViewStatii page, via the navigation menu on the left hand + of the screen. This page contains the content of the <code>Status</code> objects that were + created until now. <code>Status</code> objects are a part of logback's powerful internal + reporting framework. They allow you to see what is going on in logback, and check + that a configuration file has been parsed correctly, or that a rollover has occured as + expected. + + +image statii page + + +Visiting the View logs page does not impress much at the moment. Let us uncomment +the two parts of the config file that are below the Part I: Cyclic buffer comment. +Now reload the web-app by exiting the previous command with CTRL-C and issuing it +again: mvn jetty:run. + + + +Now, the View logs page looks prettier. Thanks to the <code>CyclicBufferAppender</code>, +this page can fetch the last events and present them through a servlet. + + + + + + + + + + + + + + + + + + + + + + + + + </body> +</document> \ No newline at end of file Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml Fri Dec 22 20:39:40 2006 @@ -513,7 +513,7 @@ <ul> Logback tries to find a file called logback.xml within the classpath. If no such file is found, it checks for another file called logback-test.xml. - In case no files are found, logback configures itself automatically thanks to the + In case none of these files are found, logback configures itself automatically thanks to the <a href="../xref/ch/qos/logback/classic/BasicConfigurator.html"><code>BasicConfigurator</code> </a> class. </ul> @@ -1215,6 +1215,64 @@ and only in that file. +<h4>Variable substitution</h4> + + +All option values admit variable substitution. The syntax of variable +substitution is similar to that of Unix shells. The string between an +opening ${ and closing } is interpreted as a key. +The value of the substituted variable can be defined as a system property +or in the configuration file itself. The value of the key +is first searched in the system properties, and if not found there, +it is then searched in the configuration file being parsed. +The corresponding value replaces ${aKey} sequence. For example, +if java.home system property is set to /home/xyz, +then every occurrence of the sequence ${java.home} will be +interpreted as /home/xyz. Recursive substitution is +also supported as the next example illustrates. + + +Example 3.12: Variable substitution (logback-examples/src/main/java/chapter3/variableSubstitution.xml) +<div class="source"><pre><configuration debug="true"> + + <appender name="FILE" + class="ch.qos.logback.core.rolling.RollingFileAppender"> + <file>${filename}</file> + + <rollingPolicy + class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> + <FileNamePattern> + ${filename}-%d{yyyy-MM-dd-HH-mm} + </FileNamePattern> + </rollingPolicy> + + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern> + %relative [%thread] %level %logger{20} %msg%n + </Pattern> + </layout> + </appender> + + + <root> + <level value="debug" /> + <appender-ref ref="FILE" /> + </root> +</configuration></pre></div> + + + + + + + + + + + + + + @@ -1231,9 +1289,7 @@ -<h4>Variable substitution</h4> -<h4></h4>

1 0

svn commit: r1148 - in logback/trunk: logback-classic logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 22 Dec '06

22 Dec '06

Author: seb Date: Fri Dec 22 15:18:05 2006 New Revision: 1148 Modified: logback/trunk/logback-classic/pom.xml logback/trunk/logback-site/src/site/xdocTemplates/manual/filters.xml Log: excluded LoggerPerfsTest from running Now mentionning the availability of AbstractMatcherFilter in the "implement your own filter" section of filter.xml Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Fri Dec 22 15:18:05 2006 @@ -111,6 +111,7 @@ <exclude>**/AllTest.java</exclude> <exclude>**/PackageTest.java</exclude> <exclude>**/SerializationPerfsTest.java</exclude> + <exclude>**/LoggerPerfTest.java</exclude> </excludes> </configuration> </plugin> Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/filters.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/filters.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/filters.xml Fri Dec 22 15:18:05 2006 @@ -160,6 +160,16 @@ getter and setter methods in the class, and you can specify the option's value in an xml element, nested within the filter element. + + + In case you want to implement a filter that provides different behaviour + depending on the result of its test (say, a filter that would accept or deny + an event depending on the content of its message), you can extend the + <a href="../xref/ch/qos/logback/core/filter/AbstractMatcherFilter.html"> + <code>AbstractMatcherFilter</code></a> class. It will provide your filter with + two attribute: OnMatch and OnMismatch, that can be configured + like any other option. + <h3>Evaluator Filters</h3> @@ -176,7 +186,8 @@ Creating a customized filter that makes use of <code>EventEvaluator</code> objects works the same way as seen previously, except that one must extend the - <code>EvaluatorFilter</code> class, instead of the <code>Filter</code> class. + <code>EvaluatorFilter</code> class, instead of the <code>Filter</code> + or <code>AbstractMatcherFilter</code> classes. <a name="EventEvaluator" />

1 0

svn commit: r1147 - in logback/trunk: logback-classic/src/main/java/ch/qos/logback/classic/filter logback-core/src/main/java/ch/qos/logback/core/filter
by noreply.seb＠qos.ch 22 Dec '06

22 Dec '06

Author: seb Date: Fri Dec 22 11:10:00 2006 New Revision: 1147 Added: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/AbstractMatcherFilter.java Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/filter/LevelFilter.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/EvaluatorFilter.java Log: Refactored filters. There is now an intermediate class under Filter to provide onMatch and onMismatch options. Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/filter/LevelFilter.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/filter/LevelFilter.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/filter/LevelFilter.java Fri Dec 22 11:10:00 2006 @@ -2,10 +2,10 @@ import ch.qos.logback.classic.Level; import ch.qos.logback.classic.spi.LoggingEvent; -import ch.qos.logback.core.filter.Filter; +import ch.qos.logback.core.filter.AbstractMatcherFilter; import ch.qos.logback.core.spi.FilterReply; -public class LevelFilter extends Filter { +public class LevelFilter extends AbstractMatcherFilter { Level level; @@ -18,9 +18,9 @@ LoggingEvent event = (LoggingEvent)eventObject; if (event.getLevel().isGreaterOrEqual(level)) { - return FilterReply.ACCEPT; + return onMatch; } else { - return FilterReply.DENY; + return onMismatch; } } Added: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/AbstractMatcherFilter.java ============================================================================== --- (empty file) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/AbstractMatcherFilter.java Fri Dec 22 11:10:00 2006 @@ -0,0 +1,29 @@ +package ch.qos.logback.core.filter; + +import ch.qos.logback.core.spi.FilterReply; + +public abstract class AbstractMatcherFilter extends Filter { + + protected FilterReply onMatch = FilterReply.NEUTRAL; + protected FilterReply onMismatch = FilterReply.NEUTRAL; + + final public void setOnMatch(String action) { + if ("NEUTRAL".equals(action)) { + onMatch = FilterReply.NEUTRAL; + } else if ("ACCEPT".equals(action)) { + onMatch = FilterReply.ACCEPT; + } else if ("DENY".equals(action)) { + onMatch = FilterReply.DENY; + } + } + + final public void setOnMismatch(String action) { + if ("NEUTRAL".equals(action)) { + onMismatch = FilterReply.NEUTRAL; + } else if ("ACCEPT".equals(action)) { + onMismatch = FilterReply.ACCEPT; + } else if ("DENY".equals(action)) { + onMismatch = FilterReply.DENY; + } + } +} Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/EvaluatorFilter.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/EvaluatorFilter.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/filter/EvaluatorFilter.java Fri Dec 22 11:10:00 2006 @@ -22,33 +22,10 @@ * @author Sébastien Pennec */ -public class EvaluatorFilter extends Filter { +public class EvaluatorFilter extends AbstractMatcherFilter { EventEvaluator evaluator; - - protected FilterReply onMatch = FilterReply.NEUTRAL; - protected FilterReply onMismatch = FilterReply.NEUTRAL; - - final public void setOnMatch(String action) { - if ("NEUTRAL".equals(action)) { - onMatch = FilterReply.NEUTRAL; - } else if ("ACCEPT".equals(action)) { - onMatch = FilterReply.ACCEPT; - } else if ("DENY".equals(action)) { - onMatch = FilterReply.DENY; - } - } - - final public void setOnMismatch(String action) { - if ("NEUTRAL".equals(action)) { - onMismatch = FilterReply.NEUTRAL; - } else if ("ACCEPT".equals(action)) { - onMismatch = FilterReply.ACCEPT; - } else if ("DENY".equals(action)) { - onMismatch = FilterReply.DENY; - } - } - + @Override public void start() { if(evaluator != null) {

1 0