May 2012 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-323) SMTPAppender does not send messages
by Lutz Huehnken (JIRA) 07 May '12

07 May '12

SMTPAppender does not send messages ----------------------------------- Key: LBCLASSIC-323 URL: http://jira.qos.ch/browse/LBCLASSIC-323 Project: logback-classic Issue Type: Bug Components: appender Affects Versions: 1.0.0 Environment: JDK 1.5 FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #0: Tue Apr 15 17:37:45 CEST 2008 amd64 Java(TM) 2 Runtime Environment, Standard Edition (build diablo-1.5.0-b01) Java HotSpot(TM) 64-Bit Server VM (build diablo-1.5.0_07-b01, mixed mode) Reporter: Lutz Huehnken Assignee: Logback dev list After upgrading from 0.9.30 to 1.0.0, the ch.qos.logback.classic.net.SMTPAppender seizes to work. It just does not send any messages anymore. This behaviour has apparently been observed by others as well and is also described in this thread: http://old.nabble.com/SMTPAppender-mail-not-sent-%28logback-1.0.0%2C-JDK-1.… It resumes working when - while making no other changes - logback is downgraded to version 0.9.30 -- 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 11

[ceki/logback] f7f651: testing email hook
by Ceki Gulcu 07 May '12

07 May '12

Branch: refs/heads/master Home: https://github.com/ceki/logback Commit: f7f651957556aee47d7caa7a1513a16658de936c https://github.com/ceki/logback/commit/f7f651957556aee47d7caa7a1513a16658de… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-07 (Mon, 07 May 2012) Changed paths: M logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java Log Message: ----------- testing email hook

1 0

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch master updated. v_1.0.3-6-g02912d9
by git-noreply＠pixie.qos.ch 07 May '12

07 May '12

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 02912d9fb0cd22e6f7112b237ae352c2d1ec886b (commit) from 54d8336c6336a5aec27df2c4a881870f62147d06 (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=02912d9fb0cd22e6f7112b23… http://github.com/ceki/logback/commit/02912d9fb0cd22e6f7112b237ae352c2d1ec8… commit 02912d9fb0cd22e6f7112b237ae352c2d1ec886b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon May 7 14:10:30 2012 +0200 testing email hook diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java index 625c61d..6c9c91b 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java @@ -6,6 +6,9 @@ import ch.qos.logback.core.joran.spi.JoranException; import org.slf4j.Logger; import org.slf4j.LoggerFactory; +/** + * + */ public class Simple { static Logger logger = LoggerFactory.getLogger(Simple.class); ----------------------------------------------------------------------- Summary of changes: .../logback/classic/issue/lbclassic323/Simple.java | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[ceki/logback] 02912d: testing email hook
by Ceki Gulcu 07 May '12

07 May '12

Branch: refs/heads/master Home: https://github.com/ceki/logback Commit: 02912d9fb0cd22e6f7112b237ae352c2d1ec886b https://github.com/ceki/logback/commit/02912d9fb0cd22e6f7112b237ae352c2d1ec… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2012-05-07 (Mon, 07 May 2012) Changed paths: M logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java Log Message: ----------- testing email hook

1 0

[JIRA] Created: (LBCORE-255) To prevent a memory leak, the ThreadLocal has been forcibly removed but still there are problems
by dIVYANG kANSARA (JIRA) 07 May '12

07 May '12

To prevent a memory leak, the ThreadLocal has been forcibly removed but still there are problems ------------------------------------------------------------------------------------------------ Key: LBCORE-255 URL: http://jira.qos.ch/browse/LBCORE-255 Project: logback-core Issue Type: Bug Environment: Linux Reporter: dIVYANG kANSARA Assignee: Logback dev list SEVERE: A web application created a ThreadLocal with key of type [null] (value [weblogic.kernel.ResettableThreadLocal$1@f6487c]) and a value of type [weblogic.kernel.ResettableThreadLocal.ThreadStorage] (value [weblogic.kernel.ResettableThreadLocal$ThreadStorage@11f824c]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@8498db]) and a value of type [weblogic.corba.client.naming.ClientORBInfo] (value [weblogic.corba.client.naming.ClientORBInfo@d9dfa4]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [null]) and a value of type [com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty] (value [com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty@f7ddc4]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [weblogic.corba.client.cluster.TargetInfo$1@1ee6665]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [org.codehaus.groovy.runtime.GroovyCategorySupport.MyThreadLocal] (value [org.codehaus.groovy.runtime.GroovyCategorySupport$MyThreadLocal@15b25e9]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@666c]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.codehaus.groovy.grails.commons.spring.ReloadAwareAutowireCapableBeanFactory$2@1405dc5]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.codehaus.groovy.grails.orm.hibernate.validation.HibernateDomainClassValidator$1@5c77e2]) and a value of type [java.util.ArrayList] (value [[]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.xml.bind.v2.runtime.Coordinator$1@13d65ad]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@11f3ccf]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.tools.xjc.reader.Ring$1@11c1dad]) and a value of type [com.sun.tools.xjc.reader.Ring] (value [com.sun.tools.xjc.reader.Ring@1bd600]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.xml.bind.v2.ClassFactory$1@1ec06a3]) and a value of type [java.util.WeakHashMap] (value [{class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse$ResourceModel=java.lang.ref.WeakReference@1cce12, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM=java.lang.ref.WeakReference@11d341d, class se.comhem.common.v2.IdentificationType=java.lang.ref.WeakReference@4893e2, class se.comhem.resource.v2.futur.entities.TvResourceType=java.lang.ref.WeakReference@e4e6e2, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse=java.lang.ref.WeakReference@1f222c4, class se.comhem.common.v2.MessageHeaderType=java.lang.ref.WeakReference@1c87a09, class se.comhem.common.v2.SourceType=java.lang.ref.WeakReference@c41706, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse$ResponseStatus=java.lang.ref.WeakReference@1c3a3ed}]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. -- 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 2

[JIRA] Created: (LBCORE-256) To prevent a memory leak, the ThreadLocal has been forcibly removed but still there are problems
by dIVYANG kANSARA (JIRA) 07 May '12

07 May '12

To prevent a memory leak, the ThreadLocal has been forcibly removed but still there are problems ------------------------------------------------------------------------------------------------ Key: LBCORE-256 URL: http://jira.qos.ch/browse/LBCORE-256 Project: logback-core Issue Type: Bug Environment: Linux Reporter: dIVYANG kANSARA Assignee: Logback dev list Hi All, Due to these severe errors the website/Webapp is not accesible intermittently. Please help. SEVERE: A web application created a ThreadLocal with key of type [null] (value [weblogic.kernel.ResettableThreadLocal$1@f6487c]) and a value of type [weblogic.kernel.ResettableThreadLocal.ThreadStorage] (value [weblogic.kernel.ResettableThreadLocal$ThreadStorage@11f824c]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [java.lang.InheritableThreadLocal] (value [java.lang.InheritableThreadLocal@8498db]) and a value of type [weblogic.corba.client.naming.ClientORBInfo] (value [weblogic.corba.client.naming.ClientORBInfo@d9dfa4]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [null]) and a value of type [com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty] (value [com.sun.xml.bind.v2.runtime.property.SingleElementLeafProperty@f7ddc4]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [weblogic.corba.client.cluster.TargetInfo$1@1ee6665]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [org.codehaus.groovy.runtime.GroovyCategorySupport.MyThreadLocal] (value [org.codehaus.groovy.runtime.GroovyCategorySupport$MyThreadLocal@15b25e9]) and a value of type [java.lang.ref.SoftReference] (value [java.lang.ref.SoftReference@666c]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.codehaus.groovy.grails.commons.spring.ReloadAwareAutowireCapableBeanFactory$2@1405dc5]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [org.codehaus.groovy.grails.orm.hibernate.validation.HibernateDomainClassValidator$1@5c77e2]) and a value of type [java.util.ArrayList] (value [[]]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.xml.bind.v2.runtime.Coordinator$1@13d65ad]) and a value of type [java.lang.Object[]] (value [[Ljava.lang.Object;@11f3ccf]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.tools.xjc.reader.Ring$1@11c1dad]) and a value of type [com.sun.tools.xjc.reader.Ring] (value [com.sun.tools.xjc.reader.Ring@1bd600]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. SEVERE: A web application created a ThreadLocal with key of type [null] (value [com.sun.xml.bind.v2.ClassFactory$1@1ec06a3]) and a value of type [java.util.WeakHashMap] (value [{class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse$ResourceModel=java.lang.ref.WeakReference@1cce12, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM=java.lang.ref.WeakReference@11d341d, class se.comhem.common.v2.IdentificationType=java.lang.ref.WeakReference@4893e2, class se.comhem.resource.v2.futur.entities.TvResourceType=java.lang.ref.WeakReference@e4e6e2, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse=java.lang.ref.WeakReference@1f222c4, class se.comhem.common.v2.MessageHeaderType=java.lang.ref.WeakReference@1c87a09, class se.comhem.common.v2.SourceType=java.lang.ref.WeakReference@c41706, class se.comhem.resource.v2.futur.ebm.GetTvResourceBySerialNumberResponseEBM$TvResourceResponse$ResponseStatus=java.lang.ref.WeakReference@1c3a3ed}]) but failed to remove it when the web application was stopped. To prevent a memory leak, the ThreadLocal has been forcibly removed. -- 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 2

[JIRA] Created: (LBCLASSIC-329) Add contextName injector for Tomcat
by Michael Osipov (JIRA) 07 May '12

07 May '12

Add contextName injector for Tomcat ----------------------------------- Key: LBCLASSIC-329 URL: http://jira.qos.ch/browse/LBCLASSIC-329 Project: logback-classic Issue Type: New Feature Components: Other Reporter: Michael Osipov Assignee: Logback dev list Attachments: LogbackContextNameListener.java Based on this StackOverflow thread, I am donating my code provides the context path as context name for LogBack. These are my dependencies: {noformat} <dependencies> <dependency> <groupId>org.apache.tomcat</groupId> <artifactId>catalina</artifactId> <version>6.0.35</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> <version>2.4</version> <scope>provided</scope> </dependency> <dependency> <groupId>commons-lang</groupId> <artifactId>commons-lang</artifactId> <version>2.6</version> </dependency> </dependencies> {noformat} -- 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 2

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch master updated. v_1.0.3-5-g54d8336
by git-noreply＠pixie.qos.ch 05 May '12

05 May '12

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 54d8336c6336a5aec27df2c4a881870f62147d06 (commit) from 6a99e92ca4ee3d622090a99b236336ca8ffef3b4 (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=54d8336c6336a5aec27df2c4… http://github.com/ceki/logback/commit/54d8336c6336a5aec27df2c4a881870f62147… commit 54d8336c6336a5aec27df2c4a881870f62147d06 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat May 5 19:09:40 2012 +0200 more edits diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index 38b073d..a940c92 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -23,8 +23,8 @@ <p>Here is a non-exhaustive list of reasons for switching to logback from log4j. Keep in mind that logback is conceptually very - similar to log4j as both projects were founded by Ceki - Gülcü. If you are already familiar with log4j, you will + similar to log4j as both projects were founded by the same + developer. If you are already familiar with log4j, you will quickly feel at home using logback.</p> <h3><a name="fasterImpl" href="#fasterImpl">Faster implementation</a></h3> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/reasonsToSwitch.html | 4 ++-- 1 files changed, 2 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_1.0.3-4-g6a99e92
by git-noreply＠pixie.qos.ch 05 May '12

05 May '12

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 6a99e92ca4ee3d622090a99b236336ca8ffef3b4 (commit) from ccc56bc6e079569a0bef20a2e639a3333e717ac5 (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=6a99e92ca4ee3d622090a99b… http://github.com/ceki/logback/commit/6a99e92ca4ee3d622090a99b236336ca8ffef… commit 6a99e92ca4ee3d622090a99b236336ca8ffef3b4 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat May 5 18:58:51 2012 +0200 minor edits diff --git a/logback-site/src/site/pages/reasonsToSwitch.html b/logback-site/src/site/pages/reasonsToSwitch.html index e8db30b..38b073d 100644 --- a/logback-site/src/site/pages/reasonsToSwitch.html +++ b/logback-site/src/site/pages/reasonsToSwitch.html @@ -97,17 +97,46 @@ a separate thread for scanning. This technical subtlety ensures that logback plays well within application servers and more generally within the JEE environment.</p> + + <h3><a name="grace" href="#grace">Graceful recovery from I/O + failures</a></h3> + + <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 get logging + working again. As soon as the file server comes back up, the + relevant logback appender will transparently and quickly recover + from the previous error condition. + </p> + <h3><a name="maxHistory" href="#maxHistory">Automatic removal of + old log archives</a></h3> - <h3><a name="lilith" href="#lilith">Lilith</a></h3> + <p>By setting the <span class="option">maxHistory</span> property + of <a + href="manual/appenders.html#TimeBasedRollingPolicy">TimeBasedRollingPolicy</a> + or <a + href="manual/appenders.html#SizeAndTimeBasedFNATP">SizeAndTimeBasedFNATP</a>, + you can control the maximum number of archived files. If your + rolling policy calls for monthly rollover and you wish to keep one + year's worth of logs, simply set the <span + class="option">maxHistory</span> property to 12. Archived log + files older than 12 months will be automatically removed. + </p> - <p><a href="http://lilith.huxhorn.de/">Lilith</a> is a logging and - access event viewer for logback. It is comparable to log4j's - 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="compression" href="#compression">Automatic + compression of archived log files</a></h3> + + <p><a + href="manual/appenders.html#RollingFileAppender">RollingFileAppender</a> + can automatically compress archived log files during + rollover. Compression always occurs asynchronously so that even + for large log files, your application is not blocked for the + duration of the compression. + </p> + + <h3><a name="prudent" href="#prudent">Prudent mode</a></h3> <p>In <a href="manual/appenders.html#prudent">prudent mode</a>, multiple <code>FileAppender</code> instances running on multiple @@ -116,13 +145,13 @@ <code>RollingFileAppender</code>. </p> - <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 get logging - working again. - </p> + <h3><a name="lilith" href="#lilith">Lilith</a></h3> + <p><a href="http://lilith.huxhorn.de/">Lilith</a> is a logging and + access event viewer for logback. It is comparable to log4j's + chainsaw, except that Lilith is designed to handle large amounts of + logging data without flinching.</p> + <h3><a name="conditional" href="#conditional">Conditional processing of configuration files</a></h3> @@ -182,19 +211,7 @@ according to user sessions, so that the logs generated by each user go into distinct log files, one log file per user. </p> - - <h3><a name="compression" href="#compression">Automatic - compression of archived log files</a></h3> - - <p><a - href="manual/appenders.html#RollingFileAppender">RollingFileAppender</a> - can automatically compress archived log files during - rollover. Compression always occurs asynchronously so that even - for large log files, your application is not blocked for the - duration of the compression. - </p> - <h3><a name="packagingData" href="#packagingData">Stack traces with packaging data</a> </h3> @@ -235,23 +252,6 @@ java.lang.Exception: 99 is invalid their IDE</a>. </p> - - <h3><a name="maxHistory" href="#maxHistory">Automatic removal of - old log archives</a></h3> - - <p>By setting the <span class="option">maxHistory</span> property - of <a - href="manual/appenders.html#TimeBasedRollingPolicy">TimeBasedRollingPolicy</a> - or <a - href="manual/appenders.html#SizeAndTimeBasedFNATP">SizeAndTimeBasedFNATP</a>, - you can control the maximum number of archived files. If your - rolling policy calls for monthly rollover and you wish to keep one - year's worth of logs, simply set the <span - class="option">maxHistory</span> property to 12. Archived log - files older than 12 months will be automatically removed. - </p> - - <h3><a name="logbackAccess" href="#logbackAccess">Logback-access, i.e. HTTP-access logging with brains, is an integral part of logback</a></h3> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/reasonsToSwitch.html | 86 +++++++++++----------- 1 files changed, 43 insertions(+), 43 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_1.0.3-3-gccc56bc
by git-noreply＠pixie.qos.ch 05 May '12

05 May '12

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 ccc56bc6e079569a0bef20a2e639a3333e717ac5 (commit) from 63ee4e4e0bad23f83cffb635147b377dc2fe3f30 (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=ccc56bc6e079569a0bef20a2… http://github.com/ceki/logback/commit/ccc56bc6e079569a0bef20a2e639a3333e717… commit ccc56bc6e079569a0bef20a2e639a3333e717ac5 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat May 5 18:27:03 2012 +0200 documentation improvements diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 2df02b0..31602ae 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -271,16 +271,6 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl </table> - <p>Given the structure of current hard drives and performance tests - we have conducted, it appears that turning off immediate flushing or - buffering of character to byte conversions have rather small impact - on performance. As such, as of logback version 0.9.19, the <span - class="prop">ImmediateFlush</span>, <span - class="prop">BufferedIO</span> and <span - class="prop">BufferSize</span> properties have been removed - without replacement. - </p> - <p>The <code>OutputStreamAppender</code> is the super-class of three other appenders, namely <code>ConsoleAppender</code>, <code>FileAppender</code> which in turn is the super class of @@ -473,9 +463,12 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl <p><span class="label notice">Immediate Flush</span> By default, each log event is immediately flushed to the underlying output - stream. For significantly increased logging throughput, you may - want to set the <span class="prop">immediateFlush</span> property - to <code>false</code> of the underlying encoder. Encoders and in + stream. This default approach is safer in the sense that logging + events are not lost in case your applicaiton exits without properly + closing appenders. However, for significantly increased logging + throughput, you may want to set the <span + class="prop">immediateFlush</span> property of the underlying + <code>Encoder</code> to <code>false</code> . Encoders and in particular <a href="encoders.html#LayoutWrappingEncoder"><code>LayoutWrappingEncoder</code></a> are described in a separate chapter.</p> diff --git a/logback-site/src/site/pages/manual/encoders.html b/logback-site/src/site/pages/manual/encoders.html index 6de5b7b..bbc504d 100644 --- a/logback-site/src/site/pages/manual/encoders.html +++ b/logback-site/src/site/pages/manual/encoders.html @@ -65,21 +65,20 @@ out. </p> - <p>At the present time (2010-03-08), - <code>PatternLayoutEncoder</code> is the only really useful - encoder. It merely wraps a <code>PatternLayout</code> which does - most of the work. Thus, it may seem that encoders do not bring much - to the table except needless complexity. However, we hope that - with the advent of new and powerful encoders this impression will - change.</p> + <p>At the present time, <code>PatternLayoutEncoder</code> is the + only really useful encoder. It merely wraps a + <code>PatternLayout</code> which does most of the work. Thus, it + may seem that encoders do not bring much to the table except + needless complexity. However, we hope that with the advent of new + and powerful encoders this impression will change.</p> <h2><a name="interface" href="#interface">Encoder interface</a></h2> <p>Encoders are responsible for transforming an incoming event into a byte array <b>and</b> writing out the resulting byte array - onto the appropriate OutputStream. Thus, encoders have total - control of what and when bytes gets written to the + onto the appropriate <code>OutputStream</code>. Thus, encoders + have total control of what and when bytes gets written to the <code>OutputStream</code> maintained by the owning appender. Here is the <a href="../xref/ch/qos/logback/core/encoder/Encoder.html">Encoder @@ -113,19 +112,18 @@ public interface Encoder<E> extends ContextAware, LifeCycle { void close() throws IOException; }</pre> - <p>As you can see, the Encoder interface consists of few methods, - but surprisingly many useful things can be accomplished with - those methods. + <p>As you can see, the <code>Encoder</code> interface consists of + few methods, but surprisingly many useful things can be + accomplished with these methods. </p> <h2><a name="LayoutWrappingEncoder" href="#LayoutWrappingEncoder">LayoutWrappingEncoder</a></h2> - <p>Until logback version 0.9.19, appenders which offered - flexibility with respect to the output format relied on - layouts. As there exists a substantial body of code based on the - layout interface, we need a way for encoders inter-operate with - layouts. <a + <p>Until logback version 0.9.19, many appenders relied on the + Layout instances to control the format of log output. As there + exists substantial amount of code based on the layout interface, + we needed a way for encoders to inter-operate with layouts. <a href="../xref/ch/qos/logback/core/encoder/LayoutWrappingEncoder.html">LayoutWrappingEncoder</a> bridges the gap between encoders and layouts. It implements the encoder interface and wraps a layout to which it delegates the @@ -167,10 +165,10 @@ public class LayoutWrappingEncoder<E> extends EncoderBase<E> { <code>OutputStream</code> given by the owning appender. By default, the <code>OutputStream</code> is immediately flushed, unless the <span class="prop">immediateFlush</span> property is - explicitly set to false. Setting the <span + explicitly set to 'false'. Setting the <span class="prop">immediateFlush</span> property to false can significantly improve logging throughput. See - <code>PatternLayoutEncoder</code> below for example. + <code>PatternLayoutEncoder</code> below for sample configuration.. </p> @@ -178,7 +176,7 @@ public class LayoutWrappingEncoder<E> extends EncoderBase<E> { href="#PatternLayoutEncoder">PatternLayoutEncoder</a></h2> <p>Given that <code>PatternLayout</code> is the most commonly used - layout, logback caters for this common use case with + layout, logback caters for this common use-case with <code>PatternLayoutEncoder</code>, an extension of <code>LayoutWrappingEncoder</code> restricted to wrapping instances of <code>PatternLayout</code>. @@ -193,6 +191,39 @@ public class LayoutWrappingEncoder<E> extends EncoderBase<E> { logback error codes</a>. </p> + <h4><span class="prop">immediateFlush</span> property</h4> + + <p>As a sub-class of <a + href="../xref/ch/qos/logback/core/encoder/LayoutWrappingEncoder.html"><code>LayoutWrappingEncoder</code></a>, + <code>PatternLayoutEncoder</code> admits the <span + class="prop">immediateFlush</span> property. The default value + for <span class="prop">immediateFlush</span> is 'true'. Immediate + flushing of the output stream ensures that logging events are + immediately written to disk and will be not lost in case your + application exits without properly closing appenders. On the + other hand, setting this property to 'false' is likely to + quadruple (your mileage may vary) logging throughput. As + mentioned previously, if <span class="prop">immediateFlush</span> + is set to 'false' and if appenders are not closed properly when + your application exits, then logging events not yet written to + disk may be lost. + </p> + + <p>Below is a sample configuration for a + <code>FileAppender</code> containing a + <code>PatternLayoutEncoder</code> with its <span + class="prop">immediateFlush</span> property set to 'false'.</p> + +<pre class="prettyprint"><appender name="FILE" class="ch.qos.logback.core.FileAppender"> + <file>foo.log</file> + <encoder> + <pattern>%d %-5level [%thread] %logger{0}: %msg%n</pattern> +  + <b><immediateFlush>false</immediateFlush></b> + </encoder> +</appender></pre> + + <h4><a name="outputPatternAsHeader" href="#outputPatternAsHeader">Output pattern string as header</a></h4> <p>In order to facilitate parsing of log files, logback can insert @@ -220,30 +251,6 @@ public class LayoutWrappingEncoder<E> extends EncoderBase<E> { <p>The line starting with "#logback.classic pattern" is newly inserted pattern line.</p> - <h4><span class="prop">immediateFlush</span> property</h4> - - <p>As a sub-class of <a - href="../xref/ch/qos/logback/core/encoder/LayoutWrappingEncoder.html"><code>LayoutWrappingEncoder</code></a>, - <code>PatternLayoutEncoder</code> admits the <span - class="prop">immediateFlush</span> property. The default value - for <span class="prop">immediateFlush</span> is 'false'. However, - by setting this property to 'false', logging throughput can be - quadrupled although your mileage may vary. - </p> - - <p>Below is a sample configuration for a - <code>FileAppender</code> containing a - <code>PatternLayoutEncoder</code> with its <span - class="prop">immediateFlush</span> property set to 'false'.</p> - -<pre class="prettyprint"><appender name="FILE" class="ch.qos.logback.core.FileAppender"> - <file>foo.log</file> - <encoder> - <pattern>%d %-5level [%thread] %logger{0}: %msg%n</pattern> -  - <b><immediateFlush>false</immediateFlush></b> - </encoder> -</appender></pre> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 19 ++--- logback-site/src/site/pages/manual/encoders.html | 95 +++++++++++---------- 2 files changed, 57 insertions(+), 57 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0