December 2006 - logback-dev

svn commit: r1121 - logback/tags/release-0.7.1
by noreply.seb＠qos.ch 19 Dec '06

19 Dec '06

Author: seb Date: Tue Dec 19 15:06:49 2006 New Revision: 1121 Removed: logback/tags/release-0.7.1/ Log: deleting wrong tag

1 0

svn commit: r1120 - logback/tags/release-0.7.1
by noreply.seb＠qos.ch 19 Dec '06

19 Dec '06

Author: seb Date: Tue Dec 19 15:05:13 2006 New Revision: 1120 Added: logback/tags/release-0.7.1/ - copied from r1119, /logback/trunk/ Log: Tagging release 0.7.1

1 0

svn commit: r1119 - in logback/trunk: . log4j-bridge logback-access logback-classic logback-core logback-examples logback-site logback-site/src/site logback-site/src/site/xdocTemplates logback-skin src/site
by noreply.seb＠qos.ch 19 Dec '06

19 Dec '06

Author: seb Date: Tue Dec 19 15:04:21 2006 New Revision: 1119 Modified: logback/trunk/log4j-bridge/pom.xml logback/trunk/logback-access/pom.xml logback/trunk/logback-classic/pom.xml logback/trunk/logback-core/pom.xml logback/trunk/logback-examples/pom.xml logback/trunk/logback-site/pom.xml logback/trunk/logback-site/src/site/site.xml logback/trunk/logback-site/src/site/xdocTemplates/news.xml logback/trunk/logback-skin/pom.xml logback/trunk/pom.xml logback/trunk/src/site/site.xml Log: version 0.7.1 updates news page Modified: logback/trunk/log4j-bridge/pom.xml ============================================================================== --- logback/trunk/log4j-bridge/pom.xml (original) +++ logback/trunk/log4j-bridge/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>log4j-bridge</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>jar</packaging> <name>Log4j Bridge Module</name> Modified: logback/trunk/logback-access/pom.xml ============================================================================== --- logback/trunk/logback-access/pom.xml (original) +++ logback/trunk/logback-access/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-access</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>jar</packaging> <name>Logback Access Module</name> Modified: logback/trunk/logback-classic/pom.xml ============================================================================== --- logback/trunk/logback-classic/pom.xml (original) +++ logback/trunk/logback-classic/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>jar</packaging> <name>Logback Classic Module</name> Modified: logback/trunk/logback-core/pom.xml ============================================================================== --- logback/trunk/logback-core/pom.xml (original) +++ logback/trunk/logback-core/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>jar</packaging> <name>Logback Core Module</name> Modified: logback/trunk/logback-examples/pom.xml ============================================================================== --- logback/trunk/logback-examples/pom.xml (original) +++ logback/trunk/logback-examples/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,14 +3,14 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>ch.qos.logback</groupId> <artifactId>logback-examples</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>jar</packaging> <name>Logback Examples Module</name> Modified: logback/trunk/logback-site/pom.xml ============================================================================== --- logback/trunk/logback-site/pom.xml (original) +++ logback/trunk/logback-site/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> <modelVersion>4.0.0</modelVersion> @@ -11,7 +11,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-site</artifactId> <packaging>jar</packaging> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <name>Logback Site</name> <url>http://logback.qos.ch</url> Modified: logback/trunk/logback-site/src/site/site.xml ============================================================================== --- logback/trunk/logback-site/src/site/site.xml (original) +++ logback/trunk/logback-site/src/site/site.xml Tue Dec 19 15:04:21 2006 @@ -4,7 +4,7 @@ <skin> <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </skin> <publishDate position="navigation-bottom" format="dd-MM-yyyy"/> Modified: logback/trunk/logback-site/src/site/xdocTemplates/news.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/news.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/news.xml Tue Dec 19 15:04:21 2006 @@ -12,6 +12,18 @@ <p>Here are the latest news about logback.</p> + <h3>December 19th, 2006 - Release of version 0.7.1</h3> + + <p> + Version 0.7.1 of logback has been released. + </p> + + <p> + This version contains more detailled information about logback access module, and + its JMX components. A <a href="access.html">dedicated page</a> explains how to configure and use logback + access in Tomcat and Jetty, and access some of its components via JMX. + </p> + <h3>December 18th, 2006 - Release of version 0.7</h3> <p> Modified: logback/trunk/logback-skin/pom.xml ============================================================================== --- logback/trunk/logback-skin/pom.xml (original) +++ logback/trunk/logback-skin/pom.xml Tue Dec 19 15:04:21 2006 @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </parent> @@ -12,7 +12,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> <packaging>jar</packaging> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <name>Logback Skin</name> <url>http://logback.qos.ch</url> Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Tue Dec 19 15:04:21 2006 @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> <packaging>pom</packaging> <name>Logback-Parent</name> Modified: logback/trunk/src/site/site.xml ============================================================================== --- logback/trunk/src/site/site.xml (original) +++ logback/trunk/src/site/site.xml Tue Dec 19 15:04:21 2006 @@ -4,7 +4,7 @@ <skin> <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> - <version>0.8-SNAPSHOT</version> + <version>0.7.1</version> </skin> <!-- <publishDate position="navigation-bottom" format="dd-MM-yyyy"/>

1 0

svn commit: r1118 - in logback/trunk: logback-examples/src/main/java/chapter3 logback-site/src/site/xdocTemplates/manual
by noreply.seb＠qos.ch 19 Dec '06

19 Dec '06

Author: seb Date: Tue Dec 19 14:44:51 2006 New Revision: 1118 Added: logback/trunk/logback-examples/src/main/java/chapter3/Foo.java logback/trunk/logback-examples/src/main/java/chapter3/MyApp1.java Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/joran.xml Log: chapter 3 in progress Added: logback/trunk/logback-examples/src/main/java/chapter3/Foo.java ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter3/Foo.java Tue Dec 19 14:44:51 2006 @@ -0,0 +1,22 @@ +/** + * Logback: the reliable, generic, fast and flexible logging framework. + * + * Copyright (C) 1999-2006, QOS.ch + * + * This library is free software, you can redistribute it and/or modify it under + * the terms of the GNU Lesser General Public License as published by the Free + * Software Foundation. + */ +package chapter3; + +import org.slf4j.Logger; +import org.slf4j.LoggerFactory; + + +public class Foo { + static final Logger logger = LoggerFactory.getLogger(Foo.class); + + public void doIt() { + logger.debug("Did it again!"); + } +} Added: logback/trunk/logback-examples/src/main/java/chapter3/MyApp1.java ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter3/MyApp1.java Tue Dec 19 14:44:51 2006 @@ -0,0 +1,31 @@ +/** + * Logback: the reliable, generic, fast and flexible logging framework. + * + * Copyright (C) 1999-2006, QOS.ch + * + * This library is free software, you can redistribute it and/or modify it under + * the terms of the GNU Lesser General Public License as published by the Free + * Software Foundation. + */ +package chapter3; + +import org.slf4j.Logger; +import org.slf4j.LoggerFactory; + +import ch.qos.logback.classic.BasicConfigurator; + + +public class MyApp1 { + final static Logger logger = LoggerFactory.getLogger(MyApp1.class); + + public static void main(String[] args) { + //Set up a simple configuration that logs on the console. + BasicConfigurator.configureDefaultContext(); + + logger.info("Entering application."); + + Foo foo = new Foo(); + foo.doIt(); + logger.info("Exiting application."); + } +} 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 Tue Dec 19 14:44:51 2006 @@ -51,6 +51,12 @@ <h2>Introduction</h2> +<p> + This document begins with a generic explanation of how the configuration + framework in logback works. Then, a second part explains how to use it + within logback to configure precisely a logging strategy. +</p> + <p>For it's configuration, logback relies on Joran, a mature, flexible and powerful configuration framework. Many of the capabilities offered by logback modules are possible thanks to Joran. @@ -63,7 +69,7 @@ nothing to do with loggers, appenders or layouts. </p> -<p>The examples for this tutorial can be found under +<p>The examples for this chapter can be found under <em>LOGBACK_HOME/logback-examples/src/main/java/chapter3</em>. </p> @@ -283,6 +289,8 @@ </p> <p>The <em>calculator2.xml</em> file is a bit more complex, but much more interesting.</p> <p>It contains the following elements:</p> + +<em>Example 3.1: Calculator configuration file (logback-examples/src/main/java/chapter3/calculator/calculator2.xml)</em> <div class="source"><pre><computation name="toto"> <literal value="7"/> <literal value="3"/> @@ -307,6 +315,8 @@ <p>Finally, a <em>calculator3.xml</em> is also provided, to demonstrate the possibility elements that contain instances of the same element. Here's the content of <em>calculator3.xml</em>:</p> + +<em>Example 3.2: Calculator configuration file (logback-examples/src/main/java/chapter3/calculator/calculator3.xml)</em> <div class="source"><pre><computation name="toto"> <computation> <literal value="7"/> @@ -354,6 +364,7 @@ <p>Using new rule declarations, the preceding example, involving the calculation, could be expressed this way:</p> +<em>Example 3.3: Configuration file using new rules on the fly (logback-examples/src/main/java/chapter3/newrule/new-rule.xml)</em> <div class="source"><pre><computation name="toto"> <new-rule pattern="*/computation/literal" actionClass="chapter3.calculator.LiteralAction"/> @@ -453,6 +464,7 @@ <p>The <em>implicit1.xml</em> file contains the following lines:</p> +<em>Example 3.4: Usage of implicit rules (logback-examples/src/main/java/chapter3/implicit/implicit1.xml)</em> <div class="source"><pre><foo> <xyz printme="true"> @@ -491,5 +503,98 @@ thousands of elements. </p> +<h2>Configuration in logback</h2> + +<div class="redBold">This section should be considered as work in progress</div> + +<p> + Logback can be configured both programmatically and thanks to an xml configuration + file. Here are the steps that logback follows to try to configure itself: +</p> + +<ul> + <p>Logback tries to find a file called <em>logback.xml</em> within the classpath.</p> + <p>If no such file is found, it checks for another file called <em>logback-test.xml</em>.</p> + <p>In case no files are found, logback configures itself automatically thanks to the + <a href="../xref/ch/qos/logback/classic/BasicConfigurator.html"><code>BasicConfigurator</code> + </a> class.</p> +</ul> +<p> + The first two checks allow for two environments to cooperate nicely. When the application + using logback is in development and test process, a special file can be used to setup + a logging environment that is developer-friendly. Once in production environment, the + presence of a <em>logback.xml</em> file overrides any <em>logback-test.xml</em> + configuration. +</p> + +<p> + The last step is meant to provide very basic logging functionnality in case no configuration + file is provided. In that case, the logging requests are output to the console. +</p> + +<h3>Manually configuring logback</h3> + +<p> + The simplest way to configure logback is by using the + <code>BasicConfigurator.configureDefaultContext()</code> method. Let us give a taste of how + this is done with the help of an imaginary application called <code>MyApp1</code>. +</p> + +<em>Example 3.5: Simple example of <code>BasicConfigurator</code> usage +<a href="../xref/chapter3/MyApp1.html">(logback-examples/src/main/java/chapter3/MyApp1.java)</a></em> +<div class="source"><pre>package chapter3; + +import org.slf4j.Logger; +import org.slf4j.LoggerFactory; + +import ch.qos.logback.classic.BasicConfigurator; + + +public class MyApp1 { + final static Logger logger = LoggerFactory.getLogger(MyApp1.class); + + public static void main(String[] args) { + //Set up a simple configuration that logs on the console. + BasicConfigurator.configureDefaultContext(); + + logger.info("Entering application."); + + Foo foo = new Foo(); + foo.doIt(); + logger.info("Exiting application."); + } +}</pre></div> + +<p> + +</p> + + + + + + + + + + + + + + + + + + + + + + + + + + + + </body> </document> \ No newline at end of file

1 0

svn commit: r1117 - logback/trunk/logback-site/src/site/xdocTemplates
by noreply.seb＠qos.ch 19 Dec '06

19 Dec '06

Author: seb Date: Tue Dec 19 14:25:09 2006 New Revision: 1117 Modified: logback/trunk/logback-site/src/site/xdocTemplates/access.xml Log: documentation update: Access.xml updated to include tomcat info, + jmx components configuration Modified: logback/trunk/logback-site/src/site/xdocTemplates/access.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/access.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/access.xml Tue Dec 19 14:25:09 2006 @@ -9,7 +9,7 @@ <body> - <h2>Access log with logback and Jetty</h2> + <h2>Access log with logback, Jetty and Tomcat</h2> <div class="author"> Authors: Ceki Gülcü, Sébastien Pennec </div> @@ -58,38 +58,73 @@ Lobgack access integrates with Servlet containers such as Jetty and Tomcat to provide HTTP-access log functionality. </p> + + <h2>Logback Access and Tomcat</h2> + + <p> + To use logback-access with Tomcat, after downlading the logback + distribution, place the files <em>logback-core-VERSION.jar</em> + and <em>logback-access-VERSION.jar</em> under $TOMCAT_HOME/common/lib + directory, where $TOMCAT_HOME is the folder where you have + installed Tomcat. We have tested logback-access module with Tomcat + version 5.5.20. + </p> + + <h3>LogbackValve</h3> + + <p> + The <a href="xref/ch/qos/logback/access/tomcat/LogbackValve.html"> + <code>ch.qos.logback.access.tomcat.LogbackValve</code></a> + class extends Tomcat's <code><a + href="http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catali…"> + ValveBase</a></code> + class. This class is used to allow external + components to be integrated into Tomcat. + </p> + + <p> + To configure Tomcat in order to use + <code>LogbackValve</code>, add the following lines + to the tomcat server configuration file, namely <em>$TOMCAT_HOME/conf/server.xml</em>: + </p> + <div class="source"><pre><Valve className="ch.qos.logback.access.tomcat.LogbackValve"/></pre></div> <p> - Integrating logback into Jetty is rather simple. Once done, you - can benefit from the power and flexibility found only in - fully-fledged logging systems. + This line need to be nested in an <em>Engine</em> element. </p> + <p> + By default, <code>LogbackValve</code> looks for a logback + configuration file called <em>logback-access.xml</em>, in the + same folder where <em>server.xml</em> is located, that is + in <em>$TOMCAT_HOME/conf/</em>. This + configuration file contains directives for configuring logback + components. Among others, you can specify the appenders where + the logging requests will be sent, and their format. Please refer + to the above description about logback access and Jetty for examples + of configuration. + </p> + <h2>Logback Access and Jetty</h2> + <p> To use logback-access with Jetty, after downlading the logback distribution, place the files <em>logback-core-VERSION.jar</em> and <em>logback-access-VERSION.jar</em> under $JETTY_HOME/lib directory, where $JETTY_HOME is the folder where you have - installed Jetty. We tested logback-access module with Jetty + installed Jetty. We have tested logback-access module with Jetty version 6.0.1. </p> - <h2>Logback's RequestLog implementation</h2> + <h3>Logback's RequestLog implementation</h3> <p> - The <code>ch.qos.logback.access.jetty.RequestLogImpl</code> + The <a href="xref/ch/qos/logback/access/jetty/RequestLogImpl.html"> + <code>ch.qos.logback.access.jetty.RequestLogImpl</code></a> class implements jetty's <code><a href="http://jetty.mortbay.org/apidocs/org/mortbay/jetty/RequestLog.html">RequestLog</a></code> interface. This interface is used by Jetty to allow external components to manage request logging. </p> -  + <p> In logback, logging destinations are called Appenders. These classes can be attached directly to <code>RequestLogImpl</code>. @@ -120,17 +155,9 @@ components. Among others, you can specify the appenders where the logging requests will be sent, and their format. </p> - - <p>Altough similar, the <em>logback-access.xml</em> file is slightly - different than the usual logback classic configuration file. - Appenders and Layouts are declared the exact same way. However, in - the access module there is no notion of loggers and consequently - loggers elements are disallowed in configuraiton files for - logback-access. - </p> - - <p>As long the path is specified, you can place the logback - configuration file in other location. Here is another example of + + <p>As long the path is specified, you can place the logback + configuration file in any location. Here is another example of jetty configuration file, with a path to the logback access configuration file. </p> @@ -143,7 +170,17 @@ </Set> </Ref></pre></div> - <h2>Example 1: logback-access configuration</h2> + <h2>Logback Access Configuration</h2> + + <p>Altough similar, the <em>logback-access.xml</em> file is slightly + different than the usual logback classic configuration file. + Appenders and Layouts are declared the exact same way. However, in + the access module there is no notion of loggers and consequently + loggers elements are disallowed in configuraiton files for + logback-access. + </p> + + <h3>Example 1: basic logback-access configuration</h3> <p> Here is a sample <em>logback-access.xml</em> file that you can immediately put to use: @@ -195,16 +232,16 @@ </layout></pre></div> - <h2>Example 2: RollingFileAppender</h2> + <h3>Example 2: RollingFileAppender</h3> <p>Another configuration file, using logback' <code>RollingFileAppender</code>, could be:</p> <div class="source"><pre><configuration> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> + <File>access.log"</File> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> - <ActiveFileName>access.log"</ActiveFileName> <FileNamePattern>access.%d{yyyy-MM-dd}.log.zip</FileNamePattern> </rollingPolicy> @@ -232,12 +269,12 @@ logback-classic module are equally possible with logback-access. </p> - <h2>PatternLayout</h2> + <h3>PatternLayout</h3> <p> An http-specific implementation of <code>PatternLayout</code> is included in the access module. The <a - href="http://logback.qos.ch/apidocs/ch/qos/logback/access/PatternLayout.html"> + href="xref/ch/qos/logback/access/PatternLayout.html"> <code>ch.qos.logback.access.PatternLayout</code></a> provides a way to format the logging output that is just as easy and flexible as the <code>PatternLayout</code> found in logback @@ -412,21 +449,158 @@ </td> </tr> </table> + + <h2>JMX Components</h2> + + <p>Logback access easily integrates with JMX servers to publish useful information + about some of its components. + </p> + + <p> + Both <code>RequestLogImpl</code> and <code>LogbackValve</code> can be + published and modified via JMX. A special filter, that we will cover + further down this document, publishes statistical views of access logs. + </p> + + + <h3>Configuring Tomcat</h3> + + <p> + Accessing JMX components with Tomcat requires to add the following lines + to the <em>$TOMCAT_HOME/bin/catalina.sh</em> configuration file: + </p> + +<div class="source"><pre>CATALINA_OPTS="-Dcom.sun.management.jmxremote" +CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.ssl=false" +CATALINA_OPTS="$CATALINA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"</pre></div> + <p> + Once started with these options, Tomcat's JMX compoenents can be access + with JConsole by issuing the following command in a shell: + </p> +<div class="source"><pre>jconsole &</pre></div> -  -  +CATALINA_OPTS="-Dcom.sun.management.jmxremote" +CATALINA_OPTS="$CATALINA_OPTS -Djavax.management.builder.initial=mx4j.server.MX4JMBeanServerBuilder" + + +CLASSPATH="$CLASSPATH":"$CATALINA_HOME"/bin/mx4j-impl.jar</pre></div> + + <p> + Finally, declare a new <code>Connector</code> in the + <em>$TOMCAT_HOME/conf/server.xml</em> file: + </p> + +<div class="source"><pre><Connector port="8050" + handler.list="mx" + mx.enabled="true" + mx.httpHost="localhost" + mx.httpPort="8082" + protocol="AJP/1.3" /></pre></div> + + <p> + Once Tomcat is started, you should be ableo to reach the JMX components by + pointing a browser to the following URL: + </p> + +<div class="source"><pre>http://host_name:8082/</pre></div> + + <h3>Configuring Jetty</h3> + + <p> + Configuring Jetty to publish JMX components requires a few modifications to the + <em>$JETTY_HOME/etc/jetty.xml</em> configuration file. Here are the elements that need to be + added: + </p> + +<div class="source"><pre><Call id="MBeanServer" class="java.lang.management.ManagementFactory" name="getPlatformMBeanServer"/> + +<Get id="Container" name="container"> + <Call name="addEventListener"> + <Arg> + <New class="org.mortbay.management.MBeanContainer"> + <Arg><Ref id="MBeanServer"/></Arg> + <Set name="managementPort">8082</Set> + <Call name="start" /> + </New> + </Arg> + </Call> +</Get></pre></div> + + <p> + Once Jetty is started with this configuration, all available components can be reviewed + at this address: + </p> +<div class="source"><pre>http://host_name:8082/</pre></div> + + <p> + Logback's <code>RequestLogImpl</code> is available, and its <code>start()</code> + and <code>stop()</code> method can be called. + </p> + + + <h3>CountingFilter</h3> + + <p> + Logback can provide a statistical view of the accesses to the server. This is done by using the + <a href="xref/ch/qos/logback/access/filter/CountingFilter.html"><code>CountingFilter</code></a> class. + </p> + + <p> + To use the <code>CountingFilter</code>, one just needs to declare it, like any + other filter: + </p> + +<div class="source"><pre><configuration> + <b><filter class="ch.qos.logback.access.filter.CountingFilter"> + <name>countingFilter</name> + </filter></b> + + <appender name="STDOUT" + class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.access.PatternLayout"> + <Pattern>%h %l %u %t \"%r\" %s %b</Pattern> + </layout> + </appender> + + <appender-ref ref="STDOUT" /> +</configuration></pre></div> + + <p> + This component registers itself to the JMX server and publishes + the following statistical figures: + </p> + + <ul> + <p>Minute average</p> + <p>Last minute's count</p> + <p>Hourly average</p> + <p>Last hour's count</p> + <p>Daily average</p> + <p>Last day's count</p> + <p>Weekly average</p> + <p>Last week's count</p> + <p>Monthly average</p> + <p>Last month's count</p> + <p>Total accesses</p> + </ul> - <h2>Troubleshooring</h2> - <p>Logback's internal error reporting system is based on Status objects. - <code>RequestLogImpl</code> uses the same <code>StatusManager</code> - as <code>LoggerContext</code> does. - </p> - --> </body> </document>

1 0

[Bug 31] New: LOGBack 0.6 Maven 2 build broken
by bugzilla-daemon＠pixie.qos.ch 18 Dec '06

18 Dec '06

http://bugzilla.qos.ch/show_bug.cgi?id=31 Summary: LOGBack 0.6 Maven 2 build broken Product: logback-general Version: unspecified Platform: All OS/Version: Windows Status: NEW Severity: blocker Priority: P1 Component: build-structure AssignedTo: logback-dev(a)qos.ch ReportedBy: tacpub(a)mac.com When I try to reference LOGBack 0.6 in my Maven 2 build, I'm unable to get it to work because the build structure is broken. Here is the message I get: Unable to get dependency information: Unable to read the metadata file for artifact 'org.slf4j:slf4j-api:jar': Cannot find parent: org.slf4j:slf4j-parent for project: org.slf4j:slf4j-api:jar:1.1.0-RC0 org.slf4j:slf4j-api-1.1.0-RC0.jar I tried to remedy this by explicitly forcing slf4j 1.1.0-RC1, but the corrupt 1.1.0-RC0 structure prevents any use of LOGBack 0.6 in Maven 2. Upgrading the LOGBack 0.6 dependency files to use slf4j 1.1.0-RC1 will eliminate this problem. I don't know of any manageable workaround short of copying LOGBack to a local repository and manually pointing it away from the broken slfrj 1.1.0-RC0. -- 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 6

svn commit: r1116 - in logback/trunk/logback-access/src/main/java/ch/qos/logback/access: filter tomcat
by noreply.seb＠qos.ch 18 Dec '06

18 Dec '06

Author: seb Date: Mon Dec 18 21:30:22 2006 New Revision: 1116 Removed: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/filter/mbeans-descriptors.xml Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/tomcat/LogbackValve.java Log: Fixed bug in LogbackValve: filter chain now called Removed unnecessary mbeans-descriptors file. Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/tomcat/LogbackValve.java ============================================================================== --- logback/trunk/logback-access/src/main/java/ch/qos/logback/access/tomcat/LogbackValve.java (original) +++ logback/trunk/logback-access/src/main/java/ch/qos/logback/access/tomcat/LogbackValve.java Mon Dec 18 21:30:22 2006 @@ -22,10 +22,12 @@ import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.spi.AppenderAttachable; import ch.qos.logback.core.spi.AppenderAttachableImpl; +import ch.qos.logback.core.spi.FilterAttachable; import ch.qos.logback.core.spi.FilterAttachableImpl; import ch.qos.logback.core.spi.FilterReply; import ch.qos.logback.core.status.ErrorStatus; import ch.qos.logback.core.status.StatusManager; +import ch.qos.logback.core.status.WarnStatus; import ch.qos.logback.core.util.StatusPrinter; /** @@ -76,7 +78,7 @@ * @author Sébastien Pennec */ public class LogbackValve extends ValveBase implements Context, - AppenderAttachable { + AppenderAttachable, FilterAttachable { public final static String DEFAULT_CONFIG_FILE = "conf" + File.separatorChar + "logback-access.xml"; @@ -121,7 +123,7 @@ } } else { getStatusManager().add( - new ErrorStatus("[" + filename + "] does not exist", this)); + new WarnStatus("[" + filename + "] does not exist", this)); } started = true; } @@ -131,9 +133,13 @@ getNext().invoke(request, response); - // System.out.println("**** LogbackValve invoke called"); TomcatServerAdapter adapter = new TomcatServerAdapter(request, response); AccessEvent accessEvent = new AccessEvent(request, response, adapter); + + if (getFilterChainDecision(accessEvent) == FilterReply.DENY) { + return; + } + // TODO better exception handling aai.appendLoopOnAppenders(accessEvent); }

1 0

[continuum] BUILD SUCCESSFUL: Logback Access Module
by John Noreplai 18 Dec '06

18 Dec '06

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Ok Previous State: Failed Started at: Mon, 18 Dec 2006 18:55:05 +0100 Finished at: Mon, 18 Dec 2006 18:55:19 +0100 Total time: 14s Build Trigger: Forced Exit code: 0 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes No files changed **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 56 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.access.db.DBAppenderTest [Server@7b1ddcde]: [Thread[main,5,main]]: checkRunning(false) entered [Server@7b1ddcde]: [Thread[main,5,main]]: checkRunning(false) exited [Server@7b1ddcde]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@7b1ddcde]: [Thread[main,5,main]]: checkRunning(false) entered [Server@7b1ddcde]: [Thread[main,5,main]]: checkRunning(false) exited [Server@7b1ddcde]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@624b035d]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@624b035d]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) entered [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) exited [Server@54bb7759]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) entered [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) exited [Server@54bb7759]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@70ba9340]: [Thread[main,5,main]]: checkRunning(false) entered [Server@70ba9340]: [Thread[main,5,main]]: checkRunning(false) exited [Server@70ba9340]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@70ba9340]: [Thread[main,5,main]]: checkRunning(false) entered [Server@70ba9340]: [Thread[main,5,main]]: checkRunning(false) exited [Server@70ba9340]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.095 sec Running ch.qos.logback.access.jetty.JettyBasicTest 2006-12-18 18:55:17.368::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2006-12-18 18:55:17.410::INFO: jetty-6.0.x 2006-12-18 18:55:17.469::INFO: Started SelectChannelConnector @ 0.0.0.0:1234 18/12/2006:18:55:17 +0100 localhost 127.0.0.1 18/12/2006:18:55:17 +0100 localhost 127.0.0.1 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.213 sec Running ch.qos.logback.access.filter.AccessStatsTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec Running ch.qos.logback.access.pattern.ConverterTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running ch.qos.logback.access.filter.StatsByDayTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec Running ch.qos.logback.access.net.URLEvaluatorTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.028 sec Running ch.qos.logback.access.net.SocketAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.133 sec Results : Tests run: 29, Failures: 0, Errors: 0, Skipped: 0 [INFO] [jar:jar] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8-SNAPSHOT.jar [INFO] Preparing source:jar [WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation. [INFO] No goals needed for project - skipping [INFO] [source:jar {execution: default}] [INFO] Building jar: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8-SNAPSHOT-sources.jar [INFO] [install:install] [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8-SNAPSHOT.jar to /root/.m2/repository/ch/qos/logback/logback-access/0.8-SNAPSHOT/logback-access-0.8-SNAPSHOT.jar [INFO] Installing /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/logback-access-0.8-SNAPSHOT-sources.jar to /root/.m2/repository/ch/qos/logback/logback-access/0.8-SNAPSHOT/logback-access-0.8-SNAPSHOT-sources.jar [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESSFUL [INFO] ------------------------------------------------------------------------ [INFO] Total time: 12 seconds [INFO] Finished at: Mon Dec 18 18:55:19 CET 2006 [INFO] Final Memory: 15M/143M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1115 - logback/trunk/src/site
by noreply.seb＠qos.ch 18 Dec '06

18 Dec '06

Author: seb Date: Mon Dec 18 18:53:17 2006 New Revision: 1115 Modified: logback/trunk/src/site/site.xml Log: version number correction Modified: logback/trunk/src/site/site.xml ============================================================================== --- logback/trunk/src/site/site.xml (original) +++ logback/trunk/src/site/site.xml Mon Dec 18 18:53:17 2006 @@ -4,7 +4,7 @@ <skin> <groupId>ch.qos.logback</groupId> <artifactId>logback-skin</artifactId> - <version>0.6-SNAPSHOT</version> + <version>0.8-SNAPSHOT</version> </skin> <!-- <publishDate position="navigation-bottom" format="dd-MM-yyyy"/>

1 0

[continuum] BUILD FAILURE: Logback Access Module
by John Noreplai 18 Dec '06

18 Dec '06

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Ok Started at: Mon, 18 Dec 2006 16:40:16 +0100 Finished at: Mon, 18 Dec 2006 16:40:26 +0100 Total time: 10s Build Trigger: Schedule Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes src/main/java/ch/qos/logback/access/jetty/RequestLogImpl.java **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Access Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 56 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/classes [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 22 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/47/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.access.db.DBAppenderTest [Server@658fb1f7]: [Thread[main,5,main]]: checkRunning(false) entered [Server@658fb1f7]: [Thread[main,5,main]]: checkRunning(false) exited [Server@658fb1f7]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@658fb1f7]: [Thread[main,5,main]]: checkRunning(false) entered [Server@658fb1f7]: [Thread[main,5,main]]: checkRunning(false) exited [Server@658fb1f7]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@624b035d]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) entered [Server@624b035d]: [Thread[main,5,main]]: checkRunning(false) exited [Server@624b035d]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2c76e369]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2c76e369]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2c76e369]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) entered [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) exited [Server@54bb7759]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) entered [Server@54bb7759]: [Thread[main,5,main]]: checkRunning(false) exited [Server@54bb7759]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.742 sec <<< FAILURE! Running ch.qos.logback.access.jetty.JettyBasicTest 2006-12-18 16:40:25.130::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2006-12-18 16:40:25.172::INFO: jetty-6.0.x 18/12/2006:16:40:25 +0100 localhost 127.0.0.1 2006-12-18 16:40:25.235::INFO: Started SelectChannelConnector @ 0.0.0.0:1234 18/12/2006:16:40:25 +0100 localhost 127.0.0.1 Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.28 sec Running ch.qos.logback.access.filter.AccessStatsTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running ch.qos.logback.access.pattern.ConverterTest Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 sec Running ch.qos.logback.access.filter.StatsByDayTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running ch.qos.logback.access.net.URLEvaluatorTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec Running ch.qos.logback.access.net.SocketAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.13 sec Results : Tests run: 29, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9 seconds [INFO] Finished at: Mon Dec 18 16:40:26 CET 2006 [INFO] Final Memory: 13M/117M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0