March 2010 - logback-dev - mailman3.qos.ch

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. release_0.9.19-3-gce0e611
by git-noreply＠pixie.qos.ch 25 Mar '10

25 Mar '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via ce0e6110ca1550aaa14c571db5f17de9accb6214 (commit) from 72c5de7d8d3fa05a4d0cccf1270cb0407f5f193a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=ce0e6110ca1550aaa14c571d… http://github.com/ceki/logback/commit/ce0e6110ca1550aaa14c571db5f17de9accb6… commit ce0e6110ca1550aaa14c571db5f17de9accb6214 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Mar 26 00:37:03 2010 +0100 - updating the docs on loggingSeparation diff --git a/logback-classic/src/test/input/joran/encoderCharset.xml b/logback-classic/src/test/input/joran/encoderCharset.xml new file mode 100644 index 0000000..2ffe366 --- /dev/null +++ b/logback-classic/src/test/input/joran/encoderCharset.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="UTF-8" ?> +<!DOCTYPE configuration> + +<configuration debug="true"> + + <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> + <encoder> + <pattern>%d - %m%n</pattern> + <charset>UTF-8</charset> + </encoder> + </appender> + + <root level="DEBUG"> + <appender-ref ref="CONSOLE" /> + </root> + +</configuration> + \ No newline at end of file diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 5b5bf09..8208a53 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -1413,12 +1413,37 @@ fileName=myApp.log </appender> <b class="green big"></included></b></pre> - <p>The file to be included can be referenced as a file, as a URL or - as a resource. To reference a file use the <span - class="attr">file</span> attribute. To reference a URL use the <span - class="attr">url</span> attribute. To reference a resource, use the - <span class="attr">resource</span> attribute. - </p> + + <p>Again, if you have note already, please note the mandatory <code + class="big green"><included></code> element.</p> + + <p>The contents to include can be referenced as a file, as a + resource, or as a URL.</p> + + <ul> + + <li><b>As a file:</b><br/> To include a file use the <span + class="attr">file</span> attribute. You can use relative paths but + note that the current directory is defined by the application and + is not necessarily related to the path of the configuration + file.</li> + + <li><p><b>As a resource:</b><br/> To include a resource, i.e a + file found on the class path, use the <span + class="attr">resource</span> attribute.</p> + + <pre class="prettyprint source"><include resource="includedConfig.xml"/></pre> + + </li> + + <li><p><b>As a URL:</b><br/> To include the contents of a URL use + the <span class="attr">url</span> attribute.</p> + + <pre class="prettyprint source"><include url="http://some.host.com/includedConfig.xml"/></pre> + + </li> + </ul> + <h3><a name="contextName" href="#contextName">Setting the context name</a></h3> diff --git a/logback-site/src/site/pages/manual/loggingSeparation.html b/logback-site/src/site/pages/manual/loggingSeparation.html index 78a2a9a..cd69a95 100644 --- a/logback-site/src/site/pages/manual/loggingSeparation.html +++ b/logback-site/src/site/pages/manual/loggingSeparation.html @@ -87,44 +87,19 @@ <p>Easy as pie.</p> - <p>Well, not exactly. First, although most do, not all containers - support child first class loading. Second, logging generated by - shared libraries will not be separated. The common idiom for - referencing a logger is via a static reference. For example, - </p> - - <pre class="prettyprint source">public class Foo { - <b>static</b> Logger logger = LoggerFactory.getLogger(Foo.class); - ... -}</pre> - - <p>Static references are both memory and CPU efficient. Only one - logger reference is used for all instances of the class. Moreover, - the logger instance is retrieved only once, when the class is - loaded into memory. Static logger references are fine as long as - they are used in classes loaded by different class - loaders. However, when a class is loaded by a parent class loader - common to multiple applications, then the shared class in question - will be loaded once and for all applications. If the shared class - contains a static logger reference, than the logger will be - retrieved once, when the shared class is loaded into memory and - initialized. Moreover, for the shared class to successfully load - into memory, slf4j and logback classed must be resolvable by the - parent class loader. This implies that slf4j and logback jar - files must also be accessible to the parent class loader. Note - that for this scenario to occur a class must be shared - <em>and</em> use slf4j. - </p> - - <p>However, if the container itself uses SLF4J and defaults to - parent-first class loading, then you need context selectors in - order to acheive logging separation. Read on. + <p>Well, not exactly. Sometimes you will be forced to place SLF4J + and logback artifacts in a place accessible from all applications, + typically because a shared library uses SLF4J. In that case, all + applications will share the same logging environment. There are + various other scenarios where a copy of SLF4J and logback + artifacts is necessarily placed at a spot where it can be seen by + all applications making logging separation by class loader + separation impossible. All hope is not lost. Please read on. </p> <h2><a name="contextSelectors" href="#contextSelectors">Context Selectors</a></h2> - <p>Logback provides a mechanism for a single instance of SLF4J and logback classes loaded into memory to provide multiple logger contexts. When you write: @@ -139,9 +114,9 @@ an instance of <a href="../apidocs/ch/qos/logback/classic/selector/ContextSelector.html">ContextSelector</a>. Note that <code>ContextSelector</code> implementations always return - instances of the <code>LoggerContext</code> class. This class - implements the <code>ILoggerFactory</code> interface. In other - words, a context selector has the option to returning any + instances <code>LoggerContext</code>. This class implements the + <code>ILoggerFactory</code> interface. In other words, a context + selector has the option to returning any <code>LoggerContext</code> instance it sees fit according to its own criteria. Hence the name context <em>selector</em>. </p> @@ -174,7 +149,11 @@ based on data available via JNDI lookup. This approach leverages JNDI data separation mandated by the J2EE specification. Thus, the same environment variable can be set to carry a different value in - different applications. + different applications. In other words, calling + <code>LoggerFactory.getLogger()</code> from different applications + will return a logger attached to a different logger context, even + if there is a single LoggerFactory class loaded into memory shared + by all applications. That's logging separation for you. </p> <p>To enable <code>ContextJNDISelector</code>, the @@ -183,7 +162,8 @@ <p class="source">-Dlogback.ContextSelector=JNDI</p> - <p>Note that JNDI is a convenient shorthand for + <p>Note that the value <code>JNDI</code> is a convenient shorthand + for <code>ch.qos.logback.classic.selector.ContextJNDISelector</code>.</p> <h3><a name="settingJNDIVariables" @@ -300,7 +280,123 @@ collection of the web-application when it is stopped or recycled.</p> - <script src="../templates/footer.js" type="text/javascript"></script> -</div> -</body> -</html> + + <h2><a name="tamingStaticRefs" href="#tamingStaticRefs">Taming + static references in shared libraries</a></h2> + + <p><code>ContextJNDISelector</code> works nicely to create logging + separation when SLF4J and logback artifacts are shared by all + applications. When <code>ContextJNDISelector</code> is active, each + call to <code>LoggerFactory.getLogger()</code> will return a logger + belonging to a logger context associated with the calling/current + application.</p> + + <p>The common idiom for referencing a logger is via a static + reference. For example, + </p> + + <pre class="prettyprint source">public class Foo { + <b>static</b> Logger logger = LoggerFactory.getLogger(Foo.class); + ... +}</pre> + + <p>Static logger references are both memory and CPU + efficient. Only one logger reference is used for all instances of + the class. Moreover, the logger instance is retrieved only once, + when the class is loaded into memory. If the host class belongs to + some application, say kenobi, then the static logger will be + attached to kenobi's logger context by virtue of + <code>ContextJNDISelector</code>. Similarly, if the host class + belongs to some other application, say yoda, then its static + logger reference will be attached to yoda's logger context, again + by virtue of <code>ContextJNDISelector</code>. + </p> + + <p>If a class, say Mustafar, belongs to a library shared by both + kenobi and yoda, as long as Mustafar has non static loggers, each + invocation of <code>LoggerFactory.getLogger()</code> will return a + logger belonging to a logger context associated with the + calling/current application. But if Mustafar has a static logger + reference, then its logger will be attach to logger context of the + application that calls it first. Thus, + <code>ContextJNDISelector</code> does not provide logging + separation in case of shared classes using static logger + references. This corner case has eluded a solution for eons.</p> + + + + <p>The only way to solve this issue transparently and perfectly + would be to introduce another level of indirection inside loggers + so that each logger-shell somehow delegated work to an inner + logger attached to the appropriate context. This approach would be + quite difficult to implement and would incur a significant + computational overhead. It is not an approach logback developpers + plan to pursue. + </p> + + + <p>One could trivially solve the "shared class static logger" + problem by moving the shared classes inside the web-apps (unshare + them). If unsharing is not possible, then let <a + href="appenders.html#SiftingAppender"><code>SiftingAppender</code></a> + separate logging using JNDI data as separation criteria. + </p> + + <p>Logback ships with a discriminator called <a + href="../xref/ch/qos/logback/classic/sift/JNDIBasedContextDiscriminator.html">JNDIBasedContextDiscriminator</a> + which returns the name of the current logger context as computed + by <code>ContextJNDISelector</code>. The + <code>SiftingAppender</code> and + <code>JNDIBasedContextDiscriminator</code> combination will create + separate appenders for each web-application. + </p> + + <pre class="prettyprint source"><configuration> + + <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> + + <appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender"> + <discriminator class="ch.qos.logback.classic.sift.JNDIBasedContextDiscriminator"> + <defaultValue>unknown</defaultValue> + </discriminator> + <sift> + <appender name="FILE-${contextName}" class="ch.qos.logback.core.FileAppender"> + <file><b>${contextName}.log</b></file> + <encoder> + <pattern>%-50(%level %logger{35}) %contextName - %msg%n</pattern> + </encoder> + </appender> + </sift> + </appender> + + <root level="DEBUG"> + <appender-ref ref="SIFT" /> + </root> +</configuration></pre> + + + <p>If kenobi and yoda are web-applications, then the above + configuration will output yoda's logs output to <em>yoda.log</em> + and kenobi's logs to <em>kenobi.log</em>, this even logs generated + by static logger refences located in shared classes.</p> + + <p>The above approach solves the logging separation problem but is + rather complex. It requires the proper installation of + <code>ContextJNDISelector</code> and mandates that appenders be + wrapped by <code>SiftingAppender</code> which is a non-trivial beast + in itself. + </p> + + <p>Note that each logging context can be confiured using the same + file or alternatively different files. The choice is up to + you. Instruicting all contexts to use the same configuiration file + is simpler as only one file has to be maintained. Maintaining a + distinct configuration file for each application is harder to + maintain but allows for more flexibility.</p> + + <p>So are we done yet? Well, not quite.</p> + + + <script src="../templates/footer.js" + type="text/javascript"></script> </div> + </body> </html> diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 6945029..cf7678c 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -33,7 +33,7 @@ <p>Fixed issue related to charsets in <code>LayoutWrappingEncoder</code> not being recognized in config - files..</p> + files.</p> ----------------------------------------------------------------------- Summary of changes: .../joran/{simple2.xml => encoderCharset.xml} | 7 +- .../src/site/pages/manual/configuration.html | 37 ++++- .../src/site/pages/manual/loggingSeparation.html | 180 +++++++++++++++----- logback-site/src/site/pages/news.html | 2 +- 4 files changed, 174 insertions(+), 52 deletions(-) copy logback-classic/src/test/input/joran/{simple2.xml => encoderCharset.xml} (68%) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBACCESS-11) Jetty 7.x support for logback-access
by Daniel Peters (JIRA) 25 Mar '10

25 Mar '10

Jetty 7.x support for logback-access ------------------------------------ Key: LBACCESS-11 URL: http://jira.qos.ch/browse/LBACCESS-11 Project: logback-access Issue Type: Improvement Affects Versions: 0.9.18 Environment: Jetty 7.0.1 - http://eclipse.org/jetty/ Reporter: Daniel Peters Assignee: Logback dev list Since Jetty moved to the Eclipse Foundation, all package names changed from "mortbay" to "eclipse", which is why logback-access 0.9.18 doesnt work with Jetty7. When configured like described in http://logback.qos.ch/access.html I get this: Caused by: java.lang.NoClassDefFoundError: org/mortbay/jetty/RequestLog Can you maybe create a 2nd Jetty RequestLogImpl that uses the new "org.eclipse.jetty"-imports? Thanks! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 5

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. release_0.9.19-2-g72c5de7
by git-noreply＠pixie.qos.ch 25 Mar '10

25 Mar '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 72c5de7d8d3fa05a4d0cccf1270cb0407f5f193a (commit) from 98cee806e36f61f770cf1d4c23063c366ae10bee (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=72c5de7d8d3fa05a4d0cccf1… http://github.com/ceki/logback/commit/72c5de7d8d3fa05a4d0cccf1270cb0407f5f1… commit 72c5de7d8d3fa05a4d0cccf1270cb0407f5f193a Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Mar 25 19:22:34 2010 +0100 - fixed charset support in Joran - doc edits diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/encoder/LayoutInsteadOfEncoderTest.java b/logback-classic/src/test/java/ch/qos/logback/classic/encoder/LayoutInsteadOfEncoderTest.java index 250c601..8231027 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/encoder/LayoutInsteadOfEncoderTest.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/encoder/LayoutInsteadOfEncoderTest.java @@ -44,8 +44,6 @@ public class LayoutInsteadOfEncoderTest { ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) loggerContext.getLogger(Logger.ROOT_LOGGER_NAME); FileAppender<ILoggingEvent> fileAppender = (FileAppender<ILoggingEvent>) root.getAppender("LIOE"); assertTrue(fileAppender.isStarted()); - - LayoutWrappingEncoder<ILoggingEvent> lwe = (LayoutWrappingEncoder<ILoggingEvent>) fileAppender.getEncoder(); - + assertTrue(fileAppender.getEncoder() instanceof LayoutWrappingEncoder); } } diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/joran/JoranConfiguratorTest.java b/logback-classic/src/test/java/ch/qos/logback/classic/joran/JoranConfiguratorTest.java index 5b495f5..07fa46f 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/joran/JoranConfiguratorTest.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/joran/JoranConfiguratorTest.java @@ -33,7 +33,9 @@ import ch.qos.logback.classic.spi.ILoggingEvent; import ch.qos.logback.classic.turbo.DebugUsersTurboFilter; import ch.qos.logback.classic.turbo.NOPTurboFilter; import ch.qos.logback.classic.turbo.TurboFilter; +import ch.qos.logback.core.ConsoleAppender; import ch.qos.logback.core.CoreConstants; +import ch.qos.logback.core.encoder.LayoutWrappingEncoder; import ch.qos.logback.core.joran.spi.JoranException; import ch.qos.logback.core.read.ListAppender; import ch.qos.logback.core.status.StatusChecker; @@ -290,4 +292,23 @@ public class JoranConfiguratorTest { assertEquals("expected \"" + expected + "\" but got " + r, expected, r); } + @Test + public void encoderCharset() throws JoranException, IOException, + InterruptedException { + + String configFileAsStr = ClassicTestConstants.JORAN_INPUT_PREFIX + + "encoderCharset.xml"; + configure(configFileAsStr); + + ConsoleAppender<ILoggingEvent> consoleAppender = (ConsoleAppender<ILoggingEvent>) root.getAppender("CONSOLE"); + assertNotNull(consoleAppender); + LayoutWrappingEncoder<ILoggingEvent> encoder = (LayoutWrappingEncoder<ILoggingEvent>) consoleAppender.getEncoder(); + + assertEquals("UTF-8", encoder.getCharset().displayName()); + + StatusChecker checker = new StatusChecker(loggerContext); + assertTrue(checker.isErrorFree()); + + } + } diff --git a/logback-core/src/main/java/ch/qos/logback/core/joran/util/PropertySetter.java b/logback-core/src/main/java/ch/qos/logback/core/joran/util/PropertySetter.java index 246a0cb..b245a7c 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/joran/util/PropertySetter.java +++ b/logback-core/src/main/java/ch/qos/logback/core/joran/util/PropertySetter.java @@ -21,7 +21,6 @@ import java.beans.MethodDescriptor; import java.beans.PropertyDescriptor; import java.lang.annotation.Annotation; import java.lang.reflect.Method; -import java.nio.charset.Charset; import ch.qos.logback.core.joran.spi.DefaultClass; import ch.qos.logback.core.joran.spi.DefaultNestedComponentRegistry; @@ -390,10 +389,6 @@ public class PropertySetter extends ContextAwareBase { return name.substring(0, 1).toUpperCase() + name.substring(1); } - boolean isOfTypeCharset(Class<?> parameterClas) { - return Charset.class.isAssignableFrom(parameterClas); - } - protected Method getMethod(String methodName) { if (methodDescriptors == null) { introspect(); diff --git a/logback-core/src/main/java/ch/qos/logback/core/joran/util/StringToObjectConverter.java b/logback-core/src/main/java/ch/qos/logback/core/joran/util/StringToObjectConverter.java index 8008f48..386bf21 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/joran/util/StringToObjectConverter.java +++ b/logback-core/src/main/java/ch/qos/logback/core/joran/util/StringToObjectConverter.java @@ -40,6 +40,8 @@ public class StringToObjectConverter { return true; } else if (parameterClass.isEnum()) { return true; + } else if (isOfTypeCharset(parameterClass)) { + return true; } return false; } diff --git a/logback-site/src/site/pages/index.html b/logback-site/src/site/pages/index.html index 0cd8ee0..9e1b898 100644 --- a/logback-site/src/site/pages/index.html +++ b/logback-site/src/site/pages/index.html @@ -23,7 +23,7 @@ <p>Logback is intended as a successor to the popular log4j project, <a href="reasonsToSwitch.html">picking up where log4j - left off</a>. + leaves off</a>. </p> <p>Logback's basic architecture is sufficiently generic so as to @@ -66,6 +66,8 @@ <li><a href="http://www.jfrog.org/products.php">Artifactory</a></li> + <li><a href="http://cia.sourceforge.net/">Citizen Intelligence Agency</a></li> + <li><a href="http://www.geomajas.org/">Geomajas</a></li> <li><a href="http://jmxmonitor.sourceforge.net/">jmxmonitor</a></li> @@ -75,9 +77,12 @@ <li><a href="http://liftweb.net/">Lift</a></li> + <li><a href="http://www.red5.org">Red5</a></li> + <li><a href="http://sonar.codehaus.org/">Sonar</a> </li> + <li><a href="http://static.springsource.org/s2-dmserver/2.0.x/user-guide/htmlsingle/user…">SpringSource dm Server</a></li> diff --git a/logback-site/src/site/pages/manual/layouts.html b/logback-site/src/site/pages/manual/layouts.html index 99a2c74..9288854 100644 --- a/logback-site/src/site/pages/manual/layouts.html +++ b/logback-site/src/site/pages/manual/layouts.html @@ -895,7 +895,7 @@ Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre> followed by the "Implementation-Version" as found in that jar's manifest will be added. This innovative technique was <a - href="http://macstrac.blogspot.com/2008/09/better-stack-traces-in-java-with-log4j…">suggested + href="http://macstrac.blogspot.com/2008/09/better-stack-traces-in-java-with-log4j…">originally suggested by James Strachan</a>. If the information is uncertain, then the class packaging data will be preceded by a tilde, i.e. the '~' character. diff --git a/logback-site/src/site/pages/manual/loggingSeparation.html b/logback-site/src/site/pages/manual/loggingSeparation.html index d366182..78a2a9a 100644 --- a/logback-site/src/site/pages/manual/loggingSeparation.html +++ b/logback-site/src/site/pages/manual/loggingSeparation.html @@ -66,7 +66,8 @@ of the container itself. </p> - <h2>The simplest and easiest approach</h2> + <h2><a name="easy" href="#easy">The simplest and easiest + approach</a></h2> <p>Assuming your container supports child first class loading, separation of logging can be accomplished by embedding a copy of @@ -112,15 +113,16 @@ parent class loader. This implies that slf4j and logback jar files must also be accessible to the parent class loader. Note that for this scenario to occur a class must be shared - <em>and</em> use slf4j, which is somewhat uncommon. + <em>and</em> use slf4j. </p> <p>However, if the container itself uses SLF4J and defaults to - parent-first class loading, then you need context selectors. Read - on. + parent-first class loading, then you need context selectors in + order to acheive logging separation. Read on. </p> - <h2>Context Selectors</h2> + <h2><a name="contextSelectors" href="#contextSelectors">Context + Selectors</a></h2> <p>Logback provides a mechanism for a single instance of SLF4J and @@ -131,7 +133,7 @@ <pre class="prettyprint source">Logger logger = LoggerFactory.getLogger("foo");</pre> <p>the <code>getLogger</code>() method in - <code>LoggerFactory</code> class asks the SLF4J binding for a + <code>LoggerFactory</code> class will ask the SLF4J binding for a <code>ILoggerFactory</code>. When SLF4J is bound to logback, the task of returning an <code>ILoggerFactory</code> is delegated to an instance of <a @@ -164,14 +166,15 @@ </p> - <h3>ContextJNDISelector</h3> + <h3><a name="ContextJNDISelector" + href="#ContextJNDISelector">ContextJNDISelector</a></h3> <p>Logback-classic ships with a selector called <code>ContextJNDISelector</code> which selects the logger context - based on data available in JNDI. This leverages JNDI data - separation mandated by the J2EE specification. The same - environment variable can be set to carry a different value in each - application. + based on data available via JNDI lookup. This approach leverages + JNDI data separation mandated by the J2EE specification. Thus, the + same environment variable can be set to carry a different value in + different applications. </p> <p>To enable <code>ContextJNDISelector</code>, the @@ -181,9 +184,11 @@ <p class="source">-Dlogback.ContextSelector=JNDI</p> <p>Note that JNDI is a convenient shorthand for - "ch.qos.logback.classic.selector.ContextJNDISelector".</p> + <code>ch.qos.logback.classic.selector.ContextJNDISelector</code>.</p> - <h3>Setting JNDI variables in applications</h3> + <h3><a name="settingJNDIVariables" + href="#settingJNDIVariables">Setting JNDI variables in + applications</a></h3> <p>In each of your applications, you need to name the logging context for the application. For a web-application, JNDI @@ -221,12 +226,13 @@ </env-entry></pre> - <h3>Configuring Tomcat for ContextJNDISelector</h3> + <h3><a name="jndiTomcat" href="#jndiTomcat">Configuring Tomcat for + ContextJNDISelector</a></h3> <p>First, place the logback jars (that is logback-classic-${project.version}.jar, logback-core-${project.version}.jar and - slf4j-api-${slff4j.version}.jar) in Tomcat's global (shared) class + slf4j-api-${slf4j.version}.jar) in Tomcat's global (shared) class folder. In Tomcat 6.x, this directory is <em>$TOMCAT_HOME/lib/</em>. </p> @@ -239,24 +245,26 @@ <p class="source">JAVA_OPTS="$JAVA_OPTS -Dlogback.ContextSelector=JNDI"</p> - <h3>Hot deploying applications</h3> - + <h3><a name="hotDeploy" href="#hotDeploy">Hot deploying + applications</a></h3> <p>When the web-application is recycled or shutdown, we strongly - recommend that the older <code>LoggerContext</code> be closed and - subsequently discarded. Logback ships with a - <code>ServletContextListener</code> called - <code>ContextDetachingSCL</code>, designed specifically for - detaching the <code>ContextSelector</code> instance associated - with the older web-application instance. In order to install it, - add the following lines to your web-applications <em>web.xml</em> + recommend that the incumbent <code>LoggerContext</code> be closed + so that it can be properly gargabe collected. Logback ships with a + <code>ServletContextListener</code> called <a + href="../xref/ch/qos/logback/classic/selector/servlet/ContextDetachingSCL.html"><code>ContextDetachingSCL</code></a>, + designed specifically for detaching the + <code>ContextSelector</code> instance associated with the older + web-application instance. It can be installed by adding the + following lines into your web-applications <em>web.xml</em> file.</p> <pre class="prettyprint source"><listener> <listener-class>ch.qos.logback.classic.selector.servlet.ContextDetachingSCL</listener-class> </listener></pre> - <h3>Better performance</h3> + <h3><a name="betterPerf" href="betterPerf">Better + performance</a></h3> <p>When <code>ContextJNDISelector</code> is active, each time a logger is retrieved, a JNDI lookup must be performed. This can @@ -264,7 +272,7 @@ non-static (aka instance) logger references. Logback ships with a servlet filter named <a href="../xref/ch/qos/logback/classic/selector/servlet/LoggerContextFilter.html">LoggerContextFilter</a>, - specifically designed to circumvent the JNDI lookup cost. It can + specifically designed to avoid the JNDI lookup cost. It can be installed by adding the following lines to your applications web.xml file.</p> diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 8e02ed1..6945029 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -26,6 +26,19 @@ the <a href="http://www.qos.ch/mailman/listinfo/announce">QOS.ch announce</a> mailing list.</p> + + <hr width="80%" align="center" /> + + <h3>March , 2010 - Release of version 0.9.20</h3> + + <p>Fixed issue related to charsets in + <code>LayoutWrappingEncoder</code> not being recognized in config + files..</p> + + + +  + <hr width="80%" align="center" /> <h3>March 24, 2010 - Release of version 0.9.19</h3> diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index f388cee..4889038 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -28,8 +28,8 @@ <h3><a name="fasterImpl" href="#fasterImpl">Faster implementation</a></h3> - <p>Based on our previous work done on log4j, logback internals - have been re-written to perform about ten times faster on certain + <p>Based on our previous work on log4j, logback internals have + been re-written to perform about ten times faster on certain critical execution paths. Not only are logback components faster, they have a smaller memory footprint as well.</p> @@ -81,7 +81,8 @@ chainsaw, except that Lilith is designed to handle large amounts of logging data without flinching.</p> - <h3><a name="grace" href="#grace">Prudent mode and graceful recovery</a></h3> + <h3><a name="grace" href="#grace">Prudent mode and graceful + recovery</a></h3> <p>In <a href="manual/appenders.html#prudent">prudent mode</a>, multiple <code>FileAppender</code> instances running on multiple @@ -93,7 +94,8 @@ <p>Logback's <code>FileAppender</code> and all its sub-classes, including <code>RollingFileAppender</code>, can gracefully recover from I/O failures. Thus, if a file server fails temporarily, you - no longer need to restart your application just to repair logging. + no longer need to restart your application just to get logging + working again. </p> @@ -183,10 +185,17 @@ java.lang.Exception: 99 is invalid stack trace, as a developper you will no longer need to ask them to send you information about the versions of packages they are using. The information will be part of the stack trace. See <a - href="manual/layouts.html#conversionWord">"%xThrowable" conversion + href="manual/layouts.html#xThrowable">"%xThrowable" conversion word</a> for details. </p> + <p>This feature can be quite helpful to the point that some users + mistakenly consider it a <a + href="http://www.jetbrains.net/devnet/message/5259058">feature of + their IDE</a>. + </p> + + <h3><a name="maxHistory" href="#maxHistory">Automatic erasure of old log archives</a></h3> @@ -203,11 +212,11 @@ java.lang.Exception: 99 is invalid </p> - <h3><a href="">In summary</a></h3> + <h3><a name="inSummary" href="#inSummary">In summary</a></h3> - <p>We have listed a small number of reasons for preferring logback - over log4j. Given that logback builds upon the log4j experience, - to put it simply, logback is just a better log4j.</p> + <p>We have listed a number of reasons for preferring logback over + log4j. Given that logback builds upon on our previous work on + log4j, simply put, logback is just a better log4j.</p> <script src="templates/footer.js" type="text/javascript"></script> </div> ----------------------------------------------------------------------- Summary of changes: .../encoder/LayoutInsteadOfEncoderTest.java | 4 +- .../classic/joran/JoranConfiguratorTest.java | 21 +++++++ .../logback/core/joran/util/PropertySetter.java | 5 -- .../core/joran/util/StringToObjectConverter.java | 2 + logback-site/src/site/pages/index.html | 7 ++- logback-site/src/site/pages/manual/layouts.html | 2 +- .../src/site/pages/manual/loggingSeparation.html | 60 +++++++++++--------- logback-site/src/site/pages/news.html | 13 ++++ logback-site/src/site/pages/reasonsToSwitch.html | 27 ++++++--- 9 files changed, 96 insertions(+), 45 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCORE-95) BurstFilter
by Ceki Gulcu (JIRA) 25 Mar '10

25 Mar '10

BurstFilter ----------- Key: LBCORE-95 URL: http://jira.qos.ch/browse/LBCORE-95 Project: logback-core Issue Type: New Feature Reporter: Ceki Gulcu Assignee: Ceki Gulcu A filter to regulate log message bursts, useful for things like throttling the number of logs sent to an e-mail appender when the database is unavailable. See http://www.qos.ch/pipermail/logback-dev/2009-March/003921.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

1 4

[JIRA] Created: (LBCLASSIC-184) Remove Cyclic Dependencies between Classic, SLF4J API and SLF4J Impl
by Gunnar Wagenknecht (JIRA) 25 Mar '10

25 Mar '10

Remove Cyclic Dependencies between Classic, SLF4J API and SLF4J Impl -------------------------------------------------------------------- Key: LBCLASSIC-184 URL: http://jira.qos.ch/browse/LBCLASSIC-184 Project: logback-classic Issue Type: Task Components: Other Affects Versions: 0.9.18 Reporter: Gunnar Wagenknecht Assignee: Logback dev list Attachments: context-selector.patch, mdc-move.patch When working with Logback as OSGi bundles I found some issues regarding cyclic dependencies. Basically, code in "org.slf4j.impl" depends on "org.slf4j.api" as well as Logback classic. This is fine. However, code in Logback classic also depends on "org.slf4j.impl". This introduces a cycle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

4 34

[JIRA] Created: (LBGENERAL-38) Javadoc is missing in logback 0.9.18 distribution
by Jean-Luc Geering (JIRA) 24 Mar '10

24 Mar '10

Javadoc is missing in logback 0.9.18 distribution ------------------------------------------------- Key: LBGENERAL-38 URL: http://jira.qos.ch/browse/LBGENERAL-38 Project: logback-general Issue Type: Task Components: build-structure Affects Versions: 0.9.18 Reporter: Jean-Luc Geering Assignee: Logback dev list http://logback.qos.ch/dist/logback-0.9.17.tar.gz(or .zip) packaged the javadoc in docs/apidocs http://logback.qos.ch/dist/logback-0.9.18.tar.gz(or .zip) doesn't contain this folder -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 6

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. release_0.9.19-1-g98cee80
by git-noreply＠pixie.qos.ch 24 Mar '10

24 Mar '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 98cee806e36f61f770cf1d4c23063c366ae10bee (commit) from 632b2a2c1dead29f4ebb504636c3a049c6fb89cf (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=98cee806e36f61f770cf1d4c… http://github.com/ceki/logback/commit/98cee806e36f61f770cf1d4c23063c366ae10… commit 98cee806e36f61f770cf1d4c23063c366ae10bee Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Mar 24 21:22:35 2010 +0100 - starting work on 0.9.20-SNAPSHOT diff --git a/logback-access/pom.xml b/logback-access/pom.xml index 2d68062..46ab56e 100644 --- a/logback-access/pom.xml +++ b/logback-access/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/logback-classic/pom.xml b/logback-classic/pom.xml index 8ecf649..d346359 100644 --- a/logback-classic/pom.xml +++ b/logback-classic/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/logback-core/pom.xml b/logback-core/pom.xml index fa2886d..3447409 100644 --- a/logback-core/pom.xml +++ b/logback-core/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/logback-examples/pom.xml b/logback-examples/pom.xml index 045e476..b08edbb 100644 --- a/logback-examples/pom.xml +++ b/logback-examples/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/logback-site/pom.xml b/logback-site/pom.xml index 568487a..712b2bd 100644 --- a/logback-site/pom.xml +++ b/logback-site/pom.xml @@ -3,7 +3,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/pom.xml b/pom.xml index 63f680f..61531d6 100755 --- a/pom.xml +++ b/pom.xml @@ -5,7 +5,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>0.9.19</version> + <version>0.9.20-SNAPSHOT</version> <packaging>pom</packaging> <name>Logback-Parent</name> diff --git a/release.sh b/release.sh index 3b7fed3..c0379a7 100644 --- a/release.sh +++ b/release.sh @@ -6,4 +6,7 @@ mvn site:site #mvn javadoc:jar mvn assembly:assembly mvn deploy -P javadocjar -mvn site:deploy -N \ No newline at end of file +mvn site:deploy -N + +#git tag -a release_${VERSION_NUMBER} +#git push --tags \ No newline at end of file ----------------------------------------------------------------------- Summary of changes: logback-access/pom.xml | 2 +- logback-classic/pom.xml | 2 +- logback-core/pom.xml | 2 +- logback-examples/pom.xml | 2 +- logback-site/pom.xml | 2 +- pom.xml | 2 +- release.sh | 5 ++++- 7 files changed, 10 insertions(+), 7 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

Release of logback v0.9.19
by Ceki Gülcü 24 Mar '10

24 Mar '10

Hello all, I am happy to announce the immediate availability of logback version 0.9.19. This version introduces a new core component called encoder which will hopefully pave the way for various new exciting features. Please refer to the the news page for precise details. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce -- Ceki

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. annotated tag, release_0.9.19, created. release_0.9.19
by git-noreply＠pixie.qos.ch 24 Mar '10

24 Mar '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The annotated tag, release_0.9.19 has been created at e555d5799c632d573965e4b8b92d45ed884a5f18 (tag) tagging 632b2a2c1dead29f4ebb504636c3a049c6fb89cf (commit) replaces v0.9.18 tagged by Ceki Gulcu on Wed Mar 24 20:51:38 2010 +0100 - Log ----------------------------------------------------------------- tagging as 0.9.19 Ceki Gulcu (112): - starting work on 0.9.19 - have osgi-build.xml refer to the lib/ folder within logback-classic minor cosmetic changes - Make ReconfigureOnChangeTest pass on Mac by taking into account the print info on test start and test stop making eclipse happy Merge branch 'master' of git@git.qos.ch:logback Added OnMarkerEvaluator. When used in conjuction with SMTPAppender, it Minor changes related to OnMarkerEvaluator added quotes I like in 2 chapters of the manual - In logback-classic ConfigurationAction, the HOSTNAME property is now - added missing hsqldb.sql files. A live version of these files can be minor comment correction - updated access.html docs to conform with Tomcat 6.0 and not 5.5. Request header names in AccessEvent (logback-access) are now stored in - added links to Support and training Fixed LBCORE-130. FileNamePattern no longer treats parenthesis as special. Fixed LBCORE-134 reported by Michael Franz. While reading - renaming test file - an attempt to make MultiThreadedRollingTest to run without any human intervention - have MultiThreadedRollingTest run consistently on a fast linux machine - increase induced delay so that - Preparing test bed for LBCORE-109. Unfortunately, due to the - Ongoing work on the test bed for LBCORE-109. Unfortunately, due to the - minor clean up of allInOneSafeMode.sh script - limit running FileAppenderResilienceTest on the host named "gimmel" Merge branch 'master' of git@git.qos.ch:/logback - removed a deprecated method WriteAppender and sub-classes now expect to work with an Encoder. The - all logback-core tests pass. Ongoing work. - all logback-classic and logback-core tests pass surefire default is to fork once - The Encoder interface is handed an ObjectStream when the - Added an example of a sample object encoder called - Initial attempt at fixing LBCORE-109 - FileAppenderResilience test passes altough the code is still a mess. - a more general description of logback omitting Ceki as founder of - marketing... mentioning packaging data in stack traces - minor refactoring of the code, testing encoding with charsets... more marketing... typo fix - measuring the differences between various fileAppender modes (imemdiateFlush, buffered io etc) - Given the IO performance is pretty good, in order to simplify usage - changing the way chapters are named in preparation for inserting a - chapter3 renamed to chapters.configuration - ongoing work on the documentation - updating the docs subsequent to the introduction of encoders ConsoleAppender must keep the underlying stream open. Skip the UnknownHostException on Mac. This fixes LBCORE-129 - working on smoother transition from layout to encoder in FileAppender - Replaced uses of TeztConstants.TEST_DIR_PREFIX with - testing the error status code emitted by OutputStreamAppender when a layout is set instead of an encoder - IO performace is hardly influenced by flushing Fixed LBCLASSIC-191 Added blurb about encoders - more tests and improvements to ResilientFileOutputStream Merge branch 'master' of git://github.com/spennec/logback - make FileAppenderResilienceTest pass attempt to improve test passing rate - chapter renumbering in the manual - minor changes - minor refactoring added link to "What's New in dm Server 2.0" presentation Editing the chapter on appenders edits to the chapter on appenders editing the manual Ongoing work on the documentation No point in printing the errors twice. - added a link to the article on making contributions. - documentation improvements - working on the docs - continued work on the documentations - improving the docs - continued work on the docs - fixing LBCLASSIC-193 Fixed LBCLASSIC-194 - change in indentation in ConsoleAppender Fixed http://jira.qos.ch/browse/LBCORE-143 - added getAppenderTracer method in SiftingAppender - SiftingAppender now exposes its AppenderTracker. Moreover, the Applied Ruediger Dohna's patch contributed in Fix LBCORE-144 - MDCInsertingServletFilter: - removed references to org.slf4j.impl package from ch.qos.logback.classic - added an import on ch.qos.logback.classic.util in - moved ContextSelectorStaticBinder from src/test to src/main. D'oh! - updated the docs Making SiftingAppender relient againt zero nested appenders and more than one nested appender. Fixed http://jira.qos.ch/browse/LBSITE-36 - additional tests and minor changes - have all tests pass - Merge branch 'master' of http://github.com/nurkiewicz/logback into dbname - added req.requestURL to MDCInsertingServletFilter Merge branch 'dbname' Fixes http://jira.qos.ch/browse/LBCLASSIC-196 - added req. MDCInsertingServletFilter - The virtual host 'gimmel' got corrupted and was resuscitated as Fixed LBCLASSIC-170 - adding H2 and Sybase support - added H2 and Sybase support - upgrade to SLF4J 1.5.11 - Adding support for H2 database - DBAppender tests pass with MySQL - tests run on oracle (host=hora) - event_id is now expected to be of type LONG. This is a first step in - table and col names converted to lower case - fixed LBCLASSIC-187 by adding 4 new columns to the logging_event table minor edit - preparing release 0.9.19 - minor changes minor edits Sebastien Pennec (1): Adding Jetty 7 support Tomasz Nurkiewicz (3): Ignore IntelliJ IDEA files [LBCLASSIC-188] Make table and column names overridable Merge branch 'master' of git://github.com/ceki/logback walterjwhite (3): fixed spelling error (downloading) fixed spelling error (downloading) fixed spelling error (specifying) ----------------------------------------------------------------------- hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v0.9.18-119-g632b2a2
by git-noreply＠pixie.qos.ch 24 Mar '10

24 Mar '10

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Logback: the generic, reliable, fast and flexible logging framework.". The branch, master has been updated via 632b2a2c1dead29f4ebb504636c3a049c6fb89cf (commit) from f6f7a40d2784bff1a81b55749431378b47345ae4 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=632b2a2c1dead29f4ebb5046… http://github.com/ceki/logback/commit/632b2a2c1dead29f4ebb504636c3a049c6fb8… commit 632b2a2c1dead29f4ebb504636c3a049c6fb89cf Author: Ceki Gulcu <ceki(a)qos.ch> Date: Wed Mar 24 20:50:08 2010 +0100 minor edits diff --git a/release.sh b/release.sh index 16ed239..3b7fed3 100644 --- a/release.sh +++ b/release.sh @@ -1,7 +1,7 @@ -# memeory aid +# memory aid mvn clean -mvn iinstall +mvn install mvn site:site #mvn javadoc:jar mvn assembly:assembly ----------------------------------------------------------------------- Summary of changes: release.sh | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0