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

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-9-gb2feaf8
by git-noreply＠pixie.qos.ch 24 Aug '10

24 Aug '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 b2feaf8b45a5d208817cacd6cbf4d8c333b0fe9f (commit) from e3a7d9cba2888e983ff5d822a012b200fad30d8f (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=b2feaf8b45a5d208817cacd6… http://github.com/ceki/logback/commit/b2feaf8b45a5d208817cacd6cbf4d8c333b0f… commit b2feaf8b45a5d208817cacd6cbf4d8c333b0fe9f Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Aug 24 23:43:45 2010 +0200 - various typo fixes diff --git a/logback-site/src/site/pages/documentation.html b/logback-site/src/site/pages/documentation.html index f965c74..53da26f 100644 --- a/logback-site/src/site/pages/documentation.html +++ b/logback-site/src/site/pages/documentation.html @@ -72,6 +72,11 @@ <h2>Articles and Presentations</h2> <ul> + + <li><a + href="http://www.nalinmakar.com/2010/07/28/logging-tests-to-separate-files/">Logging + tests to separate files</a> by Nalin Makar</li> + <li><a href="http://ekkes-corner.blogspot.com/2008/10/index-blogseries-logging-in-osgi.h…">Logging in OSGI Enterprise Applications</a>, by Ekkehard Gentz. diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 1a28588..ef275c6 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -710,7 +710,7 @@ public class MyApp3 { <code><logger></code> element</a></h4> <p>At this point should have at least some understanding of <a - href="architecture.html#effectiveLevel">level inherirance</a> and + href="architecture.html#effectiveLevel">level inheritance</a> and the <a href="architecture.html#basic_selection">basic selection rule</a>. Otherwise, and unless you are an egyptologist, logback configuration will be no more meaningful to you than diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 06dad9f..1e10a0f 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -257,7 +257,7 @@ public class HelloWorld2 { adhere to the conditions of the LGPL license or the EPL license. </p> - <p>Logback has been built and tested with the follwing JDKs.</p> + <p>Logback has been built and tested with the following JDKs.</p> <table class="bodyTable"> <tr> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/documentation.html | 5 +++++ .../src/site/pages/manual/configuration.html | 2 +- .../src/site/pages/manual/introduction.html | 2 +- 3 files changed, 7 insertions(+), 2 deletions(-) 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. v_0.9.24-8-ge3a7d9c
by git-noreply＠pixie.qos.ch 21 Aug '10

21 Aug '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 e3a7d9cba2888e983ff5d822a012b200fad30d8f (commit) from e3bdaa6cf4b14ce996b10c339d73913756a1b17d (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=e3a7d9cba2888e983ff5d822… http://github.com/ceki/logback/commit/e3a7d9cba2888e983ff5d822a012b200fad30… commit e3a7d9cba2888e983ff5d822a012b200fad30d8f Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat Aug 21 22:58:29 2010 +0200 Minor edit diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index de7769a..8b07ce9 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -2735,7 +2735,6 @@ logger.error(<b>notifyAdminMarker</b>, <em>logging_event_exception</em>. They must exist before <code>DBAppender</code> can be used. Logback ships with SQL scripts that will create the tables. They can be found in the - found in the <em>logback-classic/src/main/java/ch/qos/logback/classic/db/dialect</em> directory. There is a specific script for each of the most popular database systems. If the script for your particular type of ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCLASSIC-211) Logback fails to configure in OSGI container, when multiple configurations found
by David Riseley (JIRA) 15 Aug '10

15 Aug '10

Logback fails to configure in OSGI container, when multiple configurations found -------------------------------------------------------------------------------- Key: LBCLASSIC-211 URL: http://jira.qos.ch/browse/LBCLASSIC-211 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.20 Environment: Apache felix OSGI container, profiling with JProbe. Sun JDK 1.6.0_17 Reporter: David Riseley Assignee: Logback dev list Priority: Minor When we attempt to profile our application, which runs in an Apache Felix OSGI container, using JProbe the Logback configuration fails with the following exception: Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.IllegalArgumentException: name at sun.misc.URLClassPath$Loader.findResource(URLClassPath.java:458) at sun.misc.URLClassPath$1.next(URLClassPath.java:195) at sun.misc.URLClassPath$1.hasMoreElements(URLClassPath.java:205) at java.net.URLClassLoader$3$1.run(URLClassLoader.java:393) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader$3.next(URLClassLoader.java:390) at java.net.URLClassLoader$3.hasMoreElements(URLClassLoader.java:415) at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:27) at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:36) at sun.misc.CompoundEnumeration.next(CompoundEnumeration.java:27) at sun.misc.CompoundEnumeration.hasMoreElements(CompoundEnumeration.java:36) at ch.qos.logback.core.util.Loader.getResourceOccurenceCount(Loader.java:58) at ch.qos.logback.classic.util.ContextInitializer.multiplicityWarning(ContextInitializer.java:131) at ch.qos.logback.classic.util.ContextInitializer.statusOnResourceSearch(ContextInitializer.java:154) at ch.qos.logback.classic.util.ContextInitializer.findConfigFileURLFromSystemProperties(ContextInitializer.java:88) at ch.qos.logback.classic.util.ContextInitializer.findURLOfDefaultConfigurationFile(ContextInitializer.java:97) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:119) at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:83) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:54) at org.slf4j.LoggerFactory.getSingleton(LoggerFactory.java:230) at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:112) at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:275) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:248) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:261) at com.example.csp.gui.interfaces.logger.ABCDGUILoggerImpl.getLogger(ABCDGUILoggerImpl.java:74) at com.example.csp.gui.interfaces.logger.ABCDGUILoggerFactory.getLogger(ABCDGUILoggerFactory.java:51) at com.example.csp.gui.kernel.util.ABCDGUIKernelUtil.<clinit>(ABCDGUIKernelUtil.java:61) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.setAppBaseBundleInContext(ABCDGUIKernelContextImpl.java:207) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.init(ABCDGUIKernelContextImpl.java:93) at com.example.csp.gui.kernel.context.impl.ABCDGUIKernelContextImpl.<init>(ABCDGUIKernelContextImpl.java:58) at com.example.csp.gui.kernel.activator.impl.KernelActivatorImpl.start(KernelActivatorImpl.java:101) at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589) at org.apache.felix.framework.Felix.startBundle(Felix.java:1458) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263) at java.lang.Thread.run(Thread.java:619) SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/C:/ngawab/wab_code/code/source/wnb-common-bundles/wnb-common-client/startup-2.0.3/csp-gui-thickclient-bootstrap-2.0.3-all.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundle://4.0:1/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. After which we get no logging at all. I appreciate that this will be difficult to reproduce , and I think may be related to the "bundle://" URL format not being recognised, so I had a look at the code in ch.qos.logback.classic.util.ContextInitializer.multiplicityWarning() Currently it catches an IOExeception when calling Loader.getResourceOccurenceCount(), however from the stack trace this can also throw an. IllegalArgumentException So could : try { urlList = Loader.getResourceOccurenceCount(resourceName, classLoader); } catch (IOException e) { sm.add(new ErrorStatus("Failed to get url list for resource [" + resourceName + "]", loggerContext, e)); } Become: try { urlList = Loader.getResourceOccurenceCount(resourceName, classLoader); } catch (Exception e) { sm.add(new ErrorStatus("Failed to get url list for resource [" + resourceName + "]", loggerContext, e)); } I did try this in our environment , and the logging did get successfully configured after this change ( although it wasn't pretty.... :-> ) -- 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

[JIRA] Created: (LBCLASSIC-220) Add timeout attribute to SMTP appender
by Jeff Jensen (JIRA) 14 Aug '10

14 Aug '10

Add timeout attribute to SMTP appender -------------------------------------- Key: LBCLASSIC-220 URL: http://jira.qos.ch/browse/LBCLASSIC-220 Project: logback-classic Issue Type: Improvement Reporter: Jeff Jensen Assignee: Logback dev list Priority: Minor To prevent hangs on reading the response (default value is 0, wait forever), allow setting the timeout value. -- 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 0

[JIRA] Created: (LBCLASSIC-219) support groovy configuration in Context Selectors
by Sean McEligot (JIRA) 13 Aug '10

13 Aug '10

support groovy configuration in Context Selectors ------------------------------------------------- Key: LBCLASSIC-219 URL: http://jira.qos.ch/browse/LBCLASSIC-219 Project: logback-classic Issue Type: New Feature Components: Other Affects Versions: 0.9.24 Reporter: Sean McEligot Assignee: Logback dev list Priority: Minor Currently logback context selector only supports Joran (XML) configuration. When a groovy file is given an XML parser exception occurs. If the file ends in .groovy, the configuration should use the groovy interpreter instead of the XML Parser. INFO | jvm 1 | 2010/08/12 15:27:56 | 15:27:56,063 |-ERROR in ch.qos.logback.core.joran.event.SaxEventRecorder@13eaab - Parsing fatal error on line 1 and column 1 Here's the relevant part of the stack trace. org.xml.sax.SAXParseException: Content is not allowed in prolog. ... INFO | jvm 1 | 2010/08/12 15:27:56 | at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) INFO | jvm 1 | 2010/08/12 15:27:56 | at at ch.qos.logback.classic.selector.ContextJNDISelector.configureLoggerContextByURL(ContextJNDISelector.java:161) INFO | jvm 1 | 2010/08/12 15:27:56 | at at ch.qos.logback.classic.selector.ContextJNDISelector.getLoggerContext(ContextJNDISelector.java:105) INFO | jvm 1 | 2010/08/12 15:27:56 | at at org.slf4j.impl.StaticLoggerBinder.getLoggerFactory(StaticLoggerBinder.java:108) INFO | jvm 1 | 2010/08/12 15:27:56 | at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:273) INFO | jvm 1 | 2010/08/12 15:27:56 | at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) -- 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 1

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-7-ge3bdaa6
by git-noreply＠pixie.qos.ch 12 Aug '10

12 Aug '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 e3bdaa6cf4b14ce996b10c339d73913756a1b17d (commit) from 10b6686ab92a53f860b14953ce8493d5c3534a46 (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=e3bdaa6cf4b14ce996b10c33… http://github.com/ceki/logback/commit/e3bdaa6cf4b14ce996b10c339d73913756a1b… commit e3bdaa6cf4b14ce996b10c339d73913756a1b17d Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Aug 12 15:23:02 2010 +0200 minor editing diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 526225a..06dad9f 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -94,7 +94,7 @@ public class HelloWorld1 { } }</pre> - <p><code>HelloWorld</code> class is defined in the + <p><code>HelloWorld1</code> class is defined in the <code>chapters.introduction</code> package. It starts by importing the <a href="http://slf4j.org/api/org/slf4j/Logger.html"><code>Logger</code></a> and <a @@ -145,7 +145,7 @@ public class HelloWorld1 { class. </p> -<em>Example 1.2: Printing Logger Status (<a href="../xref/chapters/introduction/HelloWorld2.html">logback-examples/src/main/java/chapters/introduction/HelloWorld2.java</a>)</em> +<em>Example: Printing Logger Status (<a href="../xref/chapters/introduction/HelloWorld2.html">logback-examples/src/main/java/chapters/introduction/HelloWorld2.java</a>)</em> <pre class="prettyprint source">package chapters.introduction; import org.slf4j.Logger; ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/introduction.html | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCORE-165) Log file in archive created by RollingFileAppender does not have an extension
by Stijn Van Bael (JIRA) 11 Aug '10

11 Aug '10

Log file in archive created by RollingFileAppender does not have an extension ----------------------------------------------------------------------------- Key: LBCORE-165 URL: http://jira.qos.ch/browse/LBCORE-165 Project: logback-core Issue Type: Bug Components: Appender, Rolling Affects Versions: 0.9.24 Environment: Windows XP Reporter: Stijn Van Bael Assignee: Logback dev list Priority: Minor When creating a rolling file appender (see configuration below), the log file within the zipped archive has no extension. This is quite annoying on a Windows system since Windows has no clue how to open a file without extension. You have to rename the file and add the correct extension or choose the program to open over and over again. Suggested fix: make the file in the archive inherit the extension from the original log file. So for an archive named "log-2010-08-11.zip", the log file within the archive would become "log-2010-08-11.txt", since the original log file was "log.txt". <appender name="ROLLING" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>log.txt</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>log-%d{yyyy-MM-dd}.zip</fileNamePattern> <maxHistory>60</maxHistory> </rollingPolicy> <encoder> <pattern>%-4relative [%thread] %-5level %logger{35} - %msg%n</pattern> </encoder> </appender> -- 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 0

[JIRA] Created: (LBCLASSIC-218) TimeBasedRollingPolicy for DBAppender
by Clausia (JIRA) 10 Aug '10

10 Aug '10

TimeBasedRollingPolicy for DBAppender ------------------------------------- Key: LBCLASSIC-218 URL: http://jira.qos.ch/browse/LBCLASSIC-218 Project: logback-classic Issue Type: New Feature Components: appender Affects Versions: 0.9.24 Environment: Any Reporter: Clausia Assignee: Logback dev list Priority: Minor It should be nice to have a kind of TimeBasedRollingPolicy for DBAppender in order to clean logback data base tables and avoiding very large tables. -- 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 0

Security patches for Logback
by David Savage 10 Aug '10

10 Aug '10

Hi there, Sorry it's taken me so long to get this started, but I've pushed up the first change to logback to my davemssavage fork of logback [1]. This fixes the immediate security exception we were seeing when running logback in a secure JVM. I'll keep this fork open for a while in case we find other fixes. Out of interest do you use the "Pull Request" feature of git hub? Didn't want to spam you with that if it's not appropriate. Also I'm currently working on embedding Logback in an OSGi context - if I make any patches related to this are you interested in patches/new features etc? Regards, Dave [1] http://github.com/davemssavage/logback

1 0

[JIRA] Created: (LBCORE-163) Year in License
by Andres Gomez Casanova (JIRA) 07 Aug '10

07 Aug '10

Year in License --------------- Key: LBCORE-163 URL: http://jira.qos.ch/browse/LBCORE-163 Project: logback-core Issue Type: Task Affects Versions: 0.9.24 Reporter: Andres Gomez Casanova Assignee: Logback dev list Priority: Trivial I am taking the licenses of the software that I'm using, and I found that in the LICENSE.txt file, the year of logback and slf4j are 2009 and 2008, but the software has been updated after those dates. I think it should be udpated. -- 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

2 1