- logback-dev - mailman3.qos.ch

[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-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: (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: (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

[JIRA] Created: (LBACCESS-28) Could not find status manager
by seenimurugan shanmugam (JIRA) 05 May '12

05 May '12

Could not find status manager ----------------------------- Key: LBACCESS-28 URL: http://jira.qos.ch/browse/LBACCESS-28 Project: logback-access Issue Type: Bug Affects Versions: 0.9.30 Environment: tomcat 6.0.33 , mac lion os. Reporter: seenimurugan shanmugam Assignee: Logback dev list When access https://localhost:8443/lbAccessStatus i get this message on the screen ( Could not find status manager ). my configuration details. ===================== server -- tomcat 6.0.33 os ----- Mac OS X (Lion) web.xml config is ============== <servlet> <servlet-name>AccessViewStatusMessages</servlet-name> <servlet-class>ch.qos.logback.access.ViewStatusMessagesServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>AccessViewStatusMessages</servlet-name> <url-pattern>/lbAccessStatus</url-pattern> </servlet-mapping> logback-access.xml on tomcat/conf dirctory ================================== <?xml version="1.0" encoding="UTF-8"?> <configuration>  <statusListener class="ch.qos.logback.core.status.OnConsoleStatusListener" /> <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>access.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>access.%d{yyyy-MM-dd}.log.zip</fileNamePattern> </rollingPolicy> <encoder> <pattern>combined</pattern> </encoder> </appender> <appender-ref ref="FILE" /> </configuration> jar installed in tomcat/lib directory are ============================== logback-access-0.9.30.jar logback-core-0.9.30.jar when i run my web application in netbeans i can see the logback status message as ==================================================================== 18:43:39,490 |-INFO in ch.qos.logback.access.tomcat.LogbackValve[Catalina] - filename property not set. Assuming [/Users/seeni/software/apache-tomcat-6.0.33/conf/logback-access.xml] 18:43:39,556 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - Ignoring debug attribute. 18:43:39,559 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Adding status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 18:43:39,576 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 18:43:39,581 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 18:43:39,622 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use zip compression 18:43:39,624 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern access.%d{yyyy-MM-dd}.log for the active file 18:43:39,632 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'access.%d{yyyy-MM-dd}.log.zip'. 18:43:39,633 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight. 18:43:39,633 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Mon Nov 07 18:42:34 GMT 2011 18:43:39,635 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property 18:43:39,659 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: access.log 18:43:39,659 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [access.log] 18:43:39,660 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to ch.qos.logback.access.tomcat.LogbackValve[Catalina] 18:43:39,661 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration. 18:43:39,662 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@4e299813 - Registering current configuration as safe fallback point 18:43:39,490 |-INFO in ch.qos.logback.access.tomcat.LogbackValve[Catalina] - filename property not set. Assuming [/Users/seeni/software/apache-tomcat-6.0.33/conf/logback-access.xml] 18:43:39,556 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - Ignoring debug attribute. 18:43:39,559 |-INFO in ch.qos.logback.core.joran.action.StatusListenerAction - Adding status listener of type [ch.qos.logback.core.status.OnConsoleStatusListener] 18:43:39,576 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender] 18:43:39,581 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE] 18:43:39,622 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use zip compression 18:43:39,624 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy - Will use the pattern access.%d{yyyy-MM-dd}.log for the active file 18:43:39,632 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - The date pattern is 'yyyy-MM-dd' from file name pattern 'access.%d{yyyy-MM-dd}.log.zip'. 18:43:39,633 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Roll-over at midnight. 18:43:39,633 |-INFO in c.q.l.core.rolling.DefaultTimeBasedFileNamingAndTriggeringPolicy - Setting initial period to Mon Nov 07 18:42:34 GMT 2011 18:43:39,635 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.access.PatternLayoutEncoder] for [encoder] property 18:43:39,659 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: access.log 18:43:39,659 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [access.log] 18:43:39,660 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to ch.qos.logback.access.tomcat.LogbackValve[Catalina] 18:43:39,661 |-INFO in ch.qos.logback.access.joran.action.ConfigurationAction - End of configuration. 18:43:39,662 |-INFO in ch.qos.logback.access.joran.JoranConfigurator@4e299813 - Registering current configuration as safe fallback point logback status looks ok. But could not see the status on browser when i access https://localhost:8443/lbClassicStatus , it's works fine but not https://localhost:8443/lbAccessStatus I spent a whole day looking at BasicStatusManager class and all the other stuff , but no luck. is there anything i am missing or is it really a bug? 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 15

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch master updated. v_1.0.3-2-g63ee4e4
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 63ee4e4e0bad23f83cffb635147b377dc2fe3f30 (commit) from 6c689df7851d20f99afe56ed9379551c141cf0b1 (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=63ee4e4e0bad23f83cffb635… http://github.com/ceki/logback/commit/63ee4e4e0bad23f83cffb635147b377dc2fe3… commit 63ee4e4e0bad23f83cffb635147b377dc2fe3f30 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Sat May 5 13:07:20 2012 +0200 SMTPAppender now admits the asynchronousSending property diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Simple.java b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Simple.java deleted file mode 100644 index a700160..0000000 --- a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Simple.java +++ /dev/null @@ -1,34 +0,0 @@ -package ch.qos.logback.classic.issue.lbclassic232; - -import ch.qos.logback.classic.LoggerContext; -import ch.qos.logback.classic.joran.JoranConfigurator; -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); - static String DIR_PREFIX = "src/test/java/ch/qos/logback/classic/issue/lbclassic232/"; - - public static void main(String[] args) throws JoranException, InterruptedException { - init(DIR_PREFIX + "logback_smtp.xml"); - - for (int i = 0; i < 10; i++) { - logger.debug("SEE IF THIS IS LOGGED {}.", i); - } - - logger.error("trigger"); - - } - - - static void init(String file) throws JoranException { - LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); - JoranConfigurator jc = new JoranConfigurator(); - jc.setContext(loggerContext); - loggerContext.reset(); - jc.doConfigure(file); - } - -} diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Barebones.java b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Barebones.java similarity index 93% rename from logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Barebones.java rename to logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Barebones.java index f8cdf56..9704d96 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Barebones.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Barebones.java @@ -1,4 +1,4 @@ -package ch.qos.logback.classic.issue.lbclassic232; +package ch.qos.logback.classic.issue.lbclassic323; import ch.qos.logback.core.Context; import ch.qos.logback.core.ContextBase; 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 new file mode 100644 index 0000000..625c61d --- /dev/null +++ b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java @@ -0,0 +1,34 @@ +package ch.qos.logback.classic.issue.lbclassic323; + +import ch.qos.logback.classic.LoggerContext; +import ch.qos.logback.classic.joran.JoranConfigurator; +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); + static String DIR_PREFIX = "src/test/java/ch/qos/logback/classic/issue/lbclassic323/"; + + public static void main(String[] args) throws JoranException, InterruptedException { + init(DIR_PREFIX + "logback_smtp.xml"); + + for (int i = 0; i < 10; i++) { + logger.debug("SEE IF THIS IS LOGGED {}.", i); + } + logger.error("trigger"); + System.out.println("done"); + System.exit(0); + } + + + static void init(String file) throws JoranException { + LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); + JoranConfigurator jc = new JoranConfigurator(); + jc.setContext(loggerContext); + loggerContext.reset(); + jc.doConfigure(file); + } + +} diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/logback_smtp.xml b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/logback_smtp.xml similarity index 90% rename from logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/logback_smtp.xml rename to logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/logback_smtp.xml index 6b39693..12b3bb7 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/logback_smtp.xml +++ b/logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/logback_smtp.xml @@ -8,6 +8,7 @@ <subject>%logger{20} - %m</subject> <username>${destination}</username> <SSL>true</SSL> + <asynchronousSending>true</asynchronousSending> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern>%date %-5level %logger{35} - %message%n</pattern> </layout> diff --git a/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java b/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java index 68365ec..e4f1cd1 100644 --- a/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java +++ b/logback-core/src/main/java/ch/qos/logback/core/net/SMTPAppenderBase.java @@ -191,9 +191,14 @@ public abstract class SMTPAppenderBase<E> extends AppenderBase<E> { // see http://jira.qos.ch/browse/LBCLASSIC-221 cb.clear(); - // perform actual sending asynchronously - SenderRunnable senderRunnable = new SenderRunnable(cbClone, eventObject); - context.getExecutorService().execute(senderRunnable); + if(asynchronousSending) { + // perform actual sending asynchronously + SenderRunnable senderRunnable = new SenderRunnable(cbClone, eventObject); + context.getExecutorService().execute(senderRunnable); + } else { + // synchronous sending + sendBuffer(cbClone, eventObject); + } } } catch (EvaluationException ex) { errorCount++; @@ -499,6 +504,20 @@ public abstract class SMTPAppenderBase<E> extends AppenderBase<E> { this.discriminator = discriminator; } + public boolean isAsynchronousSending() { + return asynchronousSending; + } + + /** + * By default, SMTAppender transmits emails asynchronously. For synchronous email transmission set + * asynchronousSending to 'false'. + * @param asynchronousSending determines whether sending is done asynchronously or not + * @since 1.0.4 + */ + public void setAsynchronousSending(boolean asynchronousSending) { + this.asynchronousSending = asynchronousSending; + } + public void addTo(String to) { if (to == null || to.length() == 0) { throw new IllegalArgumentException("Null or empty <to> property"); diff --git a/logback-site/src/site/pages/mailinglist.html b/logback-site/src/site/pages/mailinglist.html index 821e3e3..c702465 100644 --- a/logback-site/src/site/pages/mailinglist.html +++ b/logback-site/src/site/pages/mailinglist.html @@ -144,15 +144,8 @@ </tr> </table> - <p> </p> - <h2>On IRC</h2> - - <p>We can also be reached on IRC at <span - class="big"><code>irc.freenode.net#qos.ch</code></span>. </p> - - <p> </p> <script src="templates/footer.js" type="text/javascript"></script> </div> diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 3574056..2df02b0 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -1767,7 +1767,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { <td>The host name of the SMTP server. This parameter is mandatory.</td> </tr> - <tr class="alt"> + <tr> <td><b><span class="prop">smtpPort</span></b></td> <td><code>int</code></td> <td>The port where the SMTP server is listening. Defaults to @@ -1787,7 +1787,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { </td> </tr> - <tr class="alt"> + <tr> <td><b><span class="prop">from</span></b></td> <td><code>String</code></td> <td>The originator of the email messages sent by @@ -1826,7 +1826,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { </td> </tr> - <tr class="alt"> + <tr> <td><b><span class="prop">discriminator</span></b></td> <td><code><a href="../xref/ch/qos/logback/core/sift/Discriminator.html">Discriminator</a></code></td> <td> @@ -1845,7 +1845,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { </p> </td> </tr> - <tr > + <tr> <td><b><span class="prop"><a name="smtpAppender_Evaluator" href="#smtpAppender_Evaluator">evaluator</a></span></b></td> <td><code><a @@ -1888,9 +1888,8 @@ public interface TriggeringPolicy<E> extends LifeCycle { </td> </tr> - <tr class="alt"> - <td valign="top"><b><span class="prop">cyclicBufferTracker</span></b> - </td> + <tr> + <td valign="top"><b><span class="prop">cyclicBufferTracker</span></b></td> <td><a href="../xref/ch/qos/logback/core/spi/CyclicBufferTracker.html"><code>CyclicBufferTracker</code></a> </td> <td> @@ -1906,8 +1905,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { will keep events in a cyclic buffer of size 256. You may change the size with the help of the <span class="prop">bufferSize</span> option (see below).</p> - </td> - + </td> </tr> <tr> <td><b><span class="prop">username</span></b></td> @@ -1932,7 +1930,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { parameter is set to false. </td> </tr> - <tr class="alt"> + <tr> <td><b><span class="prop">SSL</span></b></td> <td><code>boolean</code></td> <td>If this parameter is set to true, then this appender will open an SSL connection to the @@ -1951,7 +1949,7 @@ public interface TriggeringPolicy<E> extends LifeCycle { </tr> - <tr class="alt"> + <tr> <td><b>localhost</b></td> <td><code>String</code></td> <td>In case the hostname of the SMTP client is not properly @@ -1966,6 +1964,22 @@ public interface TriggeringPolicy<E> extends LifeCycle { package.</td> </tr> + <tr> + <td><b>asynchronousSending</b></td> + <td><code>boolean</code></td> + <td>This property determines whether email transmission is + done asynchronously or not. By default, the <span + class="prop">asynchronousSending</span> property is + 'true'. However, under certain circumstances asynchronous + sending may be inappropriate. For example if your application + uses <code>SMTPAppender</code> to send alerts in response to a + fatal error, and then exits, the relevant thread may not have + the time to send the alert email. In this case, set <span + class="prop">asynchronousSending</span> property to 'false' + for synchronous email transmission. + </td> + </tr> + </table> <p>The <code>SMTPAppender</code> keeps only the last 256 logging diff --git a/logback-site/src/site/pages/news.html b/logback-site/src/site/pages/news.html index 9fc982e..8e48905 100644 --- a/logback-site/src/site/pages/news.html +++ b/logback-site/src/site/pages/news.html @@ -30,7 +30,17 @@ <hr width="80%" align="center" /> - <h3>4rd of May, 2012 - Release of version 1.0.3</h3> + <h3>May, 2012 - Release of version 1.0.4</h3> + + <p><code>SMTPAppender</code> now admits the <span + class="prop">asynchronousSending</span> property, set to 'true' by + default. However, it can be set to 'false' for syncronous email + transmisison. This property was requested in <a + href="http://jira.qos.ch/browse/LBCLASSIC-323">LBCLASSIC-323</a> + by Patrick Houk.</p> + + + <h3>4th of May, 2012 - Release of version 1.0.3</h3> <p><code>PatternLayoutEncoder</code> class now admits the <span class="prop"><a ----------------------------------------------------------------------- Summary of changes: .../logback/classic/issue/lbclassic232/Simple.java | 34 ------------------ .../{lbclassic232 => lbclassic323}/Barebones.java | 2 +- .../logback/classic/issue/lbclassic323/Simple.java | 34 ++++++++++++++++++ .../logback_smtp.xml | 1 + .../ch/qos/logback/core/net/SMTPAppenderBase.java | 25 ++++++++++++-- logback-site/src/site/pages/mailinglist.html | 7 ---- logback-site/src/site/pages/manual/appenders.html | 36 ++++++++++++++------ logback-site/src/site/pages/news.html | 12 ++++++- 8 files changed, 94 insertions(+), 57 deletions(-) delete mode 100644 logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic232/Simple.java rename logback-classic/src/test/java/ch/qos/logback/classic/issue/{lbclassic232 => lbclassic323}/Barebones.java (93%) create mode 100644 logback-classic/src/test/java/ch/qos/logback/classic/issue/lbclassic323/Simple.java rename logback-classic/src/test/java/ch/qos/logback/classic/issue/{lbclassic232 => lbclassic323}/logback_smtp.xml (90%) 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-1-g6c689df
by git-noreply＠pixie.qos.ch 03 May '12

03 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 6c689df7851d20f99afe56ed9379551c141cf0b1 (commit) from 791680229b8644535b7b6e9b1aa8dc5ad1e17e0c (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=6c689df7851d20f99afe56ed… http://github.com/ceki/logback/commit/6c689df7851d20f99afe56ed9379551c141cf… commit 6c689df7851d20f99afe56ed9379551c141cf0b1 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri May 4 00:55:31 2012 +0200 start work on 1.0.4-SNAPSHOT diff --git a/logback-access/pom.xml b/logback-access/pom.xml index 5774402..478422a 100644 --- a/logback-access/pom.xml +++ b/logback-access/pom.xml @@ -7,7 +7,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> </parent> <artifactId>logback-access</artifactId> diff --git a/logback-classic/pom.xml b/logback-classic/pom.xml index 3dacd5c..0e0790f 100644 --- a/logback-classic/pom.xml +++ b/logback-classic/pom.xml @@ -7,7 +7,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> </parent> <artifactId>logback-classic</artifactId> diff --git a/logback-core/pom.xml b/logback-core/pom.xml index 3018943..63839ca 100644 --- a/logback-core/pom.xml +++ b/logback-core/pom.xml @@ -7,7 +7,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> </parent> <artifactId>logback-core</artifactId> diff --git a/logback-examples/pom.xml b/logback-examples/pom.xml index c472a4f..ab26cf3 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>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/logback-site/pom.xml b/logback-site/pom.xml index 59ba11e..cecb000 100644 --- a/logback-site/pom.xml +++ b/logback-site/pom.xml @@ -5,7 +5,7 @@ <parent> <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> diff --git a/pom.xml b/pom.xml index 53975fc..f2079de 100755 --- a/pom.xml +++ b/pom.xml @@ -6,7 +6,7 @@ <groupId>ch.qos.logback</groupId> <artifactId>logback-parent</artifactId> - <version>1.0.3</version> + <version>1.0.4-SNAPSHOT</version> <packaging>pom</packaging> <name>Logback-Parent</name> <description>logback project pom.xml file</description> ----------------------------------------------------------------------- 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 +- 6 files changed, 6 insertions(+), 6 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0