- logback-dev - mailman3.qos.ch

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

12 Oct '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 55270dc26b29a3c36ae62661bc33f4291ae71b6d (commit) from b8b8a86ea7fb2a8a35751ebbdc0929633c784303 (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=55270dc26b29a3c36ae62661… http://github.com/ceki/logback/commit/55270dc26b29a3c36ae62661bc33f4291ae71… commit 55270dc26b29a3c36ae62661bc33f4291ae71b6d Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Oct 12 22:27:28 2010 +0200 - added logger level change support in LoggerContextListener diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java b/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java index 67c7b43..5dcbf7a 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java @@ -184,6 +184,8 @@ public final class Logger implements org.slf4j.Logger, LocationAwareLogger, child.handleParentLevelChange(effectiveLevelInt); } } + // inform listeners + loggerContext.fireOnLevelChange(this, newLevel); } /** diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java b/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java index b81c581..c492817 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/LoggerContext.java @@ -308,6 +308,12 @@ public class LoggerContext extends ContextBase implements ILoggerFactory, return new ArrayList<LoggerContextListener>(loggerContextListenerList); } + void fireOnLevelChange(Logger logger, Level level) { + for (LoggerContextListener listener : loggerContextListenerList) { + listener.onLevelChange(logger, level); + } + } + private void fireOnReset() { for (LoggerContextListener listener : loggerContextListenerList) { listener.onReset(this); diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/jmx/JMXConfigurator.java b/logback-classic/src/main/java/ch/qos/logback/classic/jmx/JMXConfigurator.java index 4bada7e..26edee4 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/jmx/JMXConfigurator.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/jmx/JMXConfigurator.java @@ -261,6 +261,10 @@ public class JMXConfigurator extends ContextAwareBase implements stop(); } + public void onLevelChange(Logger logger, Level level) { + // nothing to do + } + public void onReset(LoggerContext context) { addInfo("onReset() method called JMXActivator [" + objectNameAsString + "]"); } diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextListener.java b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextListener.java index 58fdf48..21fc330 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextListener.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/spi/LoggerContextListener.java @@ -13,6 +13,8 @@ */ package ch.qos.logback.classic.spi; +import ch.qos.logback.classic.Level; +import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.LoggerContext; public interface LoggerContextListener { @@ -27,4 +29,5 @@ public interface LoggerContextListener { public void onStart(LoggerContext context); public void onReset(LoggerContext context); public void onStop(LoggerContext context); + public void onLevelChange(Logger logger, Level level); } diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/spi/BasicContextListener.java b/logback-classic/src/test/java/ch/qos/logback/classic/spi/BasicContextListener.java index 4e32c1e..5cec4cb 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/spi/BasicContextListener.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/spi/BasicContextListener.java @@ -13,14 +13,18 @@ */ package ch.qos.logback.classic.spi; +import ch.qos.logback.classic.Level; +import ch.qos.logback.classic.Logger; import ch.qos.logback.classic.LoggerContext; public class BasicContextListener implements LoggerContextListener { - enum UpdateType { NONE, START, RESET, STOP}; + enum UpdateType { NONE, START, RESET, STOP , LEVEL_CHANGE}; UpdateType updateType = UpdateType.NONE; LoggerContext context; + Logger logger; + Level level; boolean resetResistant; @@ -42,8 +46,15 @@ public class BasicContextListener implements LoggerContextListener { updateType = UpdateType.STOP;; this.context = context; } - + public boolean isResetResistant() { return resetResistant; } + + public void onLevelChange(Logger logger, Level level) { + updateType = UpdateType.LEVEL_CHANGE; + this.logger = logger; + this.level = level; + } + } diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/spi/ContextListenerTest.java b/logback-classic/src/test/java/ch/qos/logback/classic/spi/ContextListenerTest.java index 95c3186..9d10c90 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/spi/ContextListenerTest.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/spi/ContextListenerTest.java @@ -15,17 +15,19 @@ package ch.qos.logback.classic.spi; import static org.junit.Assert.assertEquals; +import ch.qos.logback.classic.Level; +import ch.qos.logback.classic.Logger; import org.junit.Before; import org.junit.Test; import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.spi.BasicContextListener.UpdateType; -public class ContextListenerTest { - +public class ContextListenerTest { + LoggerContext context; BasicContextListener listener; - + @Before public void setUp() throws Exception { context = new LoggerContext(); @@ -61,4 +63,21 @@ public class ContextListenerTest { assertEquals(UpdateType.START, listener.updateType); assertEquals(listener.context, context); } + + void checkLevelChange(String loggerName, Level level) { + Logger logger = context.getLogger(loggerName); + logger.setLevel(level); + + assertEquals(UpdateType.LEVEL_CHANGE, listener.updateType); + assertEquals(listener.logger, logger); + assertEquals(listener.level, level); + + } + + @Test + public void testLevelChange() { + checkLevelChange("a", Level.INFO); + checkLevelChange("a.b", Level.ERROR); + checkLevelChange("a.b.c", Level.DEBUG); + } } diff --git a/logback-site/src/site/pages/manual/encoders.html b/logback-site/src/site/pages/manual/encoders.html index 237bfd9..70dc3de 100644 --- a/logback-site/src/site/pages/manual/encoders.html +++ b/logback-site/src/site/pages/manual/encoders.html @@ -65,12 +65,13 @@ out. - At present time (2010-03-08), <code>PatternLayotEncoder</code> - is the only really useful encoder. It merely wraps a - <code>PatternLayout</code> which does most of the work. Thus, 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. + 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, 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. <h2><a name="interface" href="#interface">Encoder interface</a></h2> @@ -185,6 +186,10 @@ public class LayoutWrappingEncoder<E> extends EncoderBase<E> { logback error codes</a>. + + + <script src="../templates/footer.js" type="text/javascript"></script> + </div> </body> </html> ----------------------------------------------------------------------- Summary of changes: .../main/java/ch/qos/logback/classic/Logger.java | 2 + .../java/ch/qos/logback/classic/LoggerContext.java | 6 ++++ .../qos/logback/classic/jmx/JMXConfigurator.java | 4 +++ .../logback/classic/spi/LoggerContextListener.java | 3 ++ .../logback/classic/spi/BasicContextListener.java | 15 ++++++++++- .../logback/classic/spi/ContextListenerTest.java | 25 +++++++++++++++++-- logback-site/src/site/pages/manual/encoders.html | 17 ++++++++---- 7 files changed, 61 insertions(+), 11 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-25-gb8b8a86
by git-noreply＠pixie.qos.ch 12 Oct '10

12 Oct '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 b8b8a86ea7fb2a8a35751ebbdc0929633c784303 (commit) via c3c5476f1d20eca1a7d5681a1854a567880ee4d3 (commit) from f25fb2e781923f5569795de6828cebb911c9451b (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=b8b8a86ea7fb2a8a35751ebb… http://github.com/ceki/logback/commit/b8b8a86ea7fb2a8a35751ebbdc0929633c784… commit b8b8a86ea7fb2a8a35751ebbdc0929633c784303 Merge: c3c5476 f25fb2e Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Oct 12 22:22:52 2010 +0200 Merge branch 'master' of git.qos.ch:logback http://git.qos.ch/gitweb/?p=logback.git;a=commit;h=c3c5476f1d20eca1a7d5681a… http://github.com/ceki/logback/commit/c3c5476f1d20eca1a7d5681a1854a567880ee… commit c3c5476f1d20eca1a7d5681a1854a567880ee4d3 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Oct 12 22:22:10 2010 +0200 - adding the capability to listen to level changes diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/LoggerContextListenerAction.java b/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/LoggerContextListenerAction.java new file mode 100644 index 0000000..fe6890e --- /dev/null +++ b/logback-classic/src/main/java/ch/qos/logback/classic/joran/action/LoggerContextListenerAction.java @@ -0,0 +1,80 @@ +/** + * Logback: the reliable, generic, fast and flexible logging framework. + * Copyright (C) 1999-2009, QOS.ch. All rights reserved. + * + * This program and the accompanying materials are dual-licensed under + * either the terms of the Eclipse Public License v1.0 as published by + * the Eclipse Foundation + * + * or (per the licensee's choosing) + * + * under the terms of the GNU Lesser General Public License version 2.1 + * as published by the Free Software Foundation. + */ +package ch.qos.logback.classic.joran.action; + +import java.lang.management.ManagementFactory; + +import javax.management.MBeanServer; +import javax.management.ObjectName; + +import ch.qos.logback.classic.spi.LoggerContextListener; +import ch.qos.logback.core.boolex.EventEvaluator; +import ch.qos.logback.core.spi.LifeCycle; +import org.xml.sax.Attributes; + +import ch.qos.logback.classic.LoggerContext; +import ch.qos.logback.classic.jmx.JMXConfigurator; +import ch.qos.logback.classic.jmx.MBeanUtil; +import ch.qos.logback.core.joran.action.Action; +import ch.qos.logback.core.joran.spi.ActionException; +import ch.qos.logback.core.joran.spi.InterpretationContext; +import ch.qos.logback.core.util.OptionHelper; + +public class LoggerContextListenerAction extends Action { + boolean inError = false; + LoggerContextListener lcl; + + @Override + public void begin(InterpretationContext ec, String name, Attributes attributes) + throws ActionException { + + inError = false; + + String className = attributes.getValue(CLASS_ATTRIBUTE); + if (OptionHelper.isEmpty(className)) { + addError("Mandatory \"" + CLASS_ATTRIBUTE + + "\" attribute not set for <loggerContextListener> element"); + inError = true; + return; + } + + try { + lcl = (LoggerContextListener) OptionHelper.instantiateByClassName( + className, LoggerContextListener.class, context); + + ec.pushObject(lcl); + addInfo("Adding LoggerContextListener of type [" + className + + "] to the object stack"); + + } catch (Exception oops) { + inError = true; + addError("Could not create LoggerContextListener of type " + className + "].", oops); + } + } + + @Override + public void end(InterpretationContext ec, String name) throws ActionException { + if (inError) { + return; + } + Object o = ec.peekObject(); + + if (o != lcl) { + addWarn("The object on the top the of the stack is not the LoggerContextListener pushed earlier."); + } else { + ec.popObject(); + } + } + +} ----------------------------------------------------------------------- Summary of changes: .../joran/action/LoggerContextListenerAction.java | 80 ++++++++++++++++++++ 1 files changed, 80 insertions(+), 0 deletions(-) create mode 100644 logback-classic/src/main/java/ch/qos/logback/classic/joran/action/LoggerContextListenerAction.java 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-23-gf25fb2e
by git-noreply＠pixie.qos.ch 11 Oct '10

11 Oct '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 f25fb2e781923f5569795de6828cebb911c9451b (commit) from 909a8e44a8b766582624b62a32631ca348c70d49 (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=f25fb2e781923f5569795de6… http://github.com/ceki/logback/commit/f25fb2e781923f5569795de6828cebb911c94… commit f25fb2e781923f5569795de6828cebb911c9451b Author: Ceki Gulcu <ceki(a)qos.ch> Date: Mon Oct 11 17:40:44 2010 +0200 typo fix diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 9782baf..2d0db3e 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -242,7 +242,7 @@ public class Foo { Example: Basic configuration file (logback-examples/src/main/java/chapters/configuration/sample0.xml) - View as .grovvy + View as .groovy <pre id="sample0" class="prettyprint source"><configuration> @@ -338,7 +338,7 @@ public class Foo { Example: Basic configuration file using debug mode (logback-examples/src/main/java/chapters/configuration/sample1.xml) - View as .grovvy + View as .groovy <pre id="sample1" class="prettyprint source"> <configuration debug="true"> @@ -416,7 +416,7 @@ public class Foo { file and automatic re-configuration (logback-examples/src/main/java/chapters/configuration/scan1.xml) - View as .grovvy + View as .groovy <pre id="scan1" class="prettyprint source"> <configuration scan="true"> ... @@ -432,7 +432,7 @@ public class Foo { Example: Specifying a different scanning period (logback-examples/src/main/java/chapters/configuration/scan2.xml) - View as .grovvy + View as .groovy <pre id="scan2" class="prettyprint source"> <configuration scan="true" scanPeriod="30 seconds" > ... ----------------------------------------------------------------------- Summary of changes: .../src/site/pages/manual/configuration.html | 8 ++++---- 1 files changed, 4 insertions(+), 4 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-22-g909a8e4
by git-noreply＠pixie.qos.ch 08 Oct '10

08 Oct '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 909a8e44a8b766582624b62a32631ca348c70d49 (commit) from d52ee5dcef840f3083950b0374bc5b06f9dfae97 (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=909a8e44a8b766582624b62a… http://github.com/ceki/logback/commit/909a8e44a8b766582624b62a32631ca348c70… commit 909a8e44a8b766582624b62a32631ca348c70d49 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Fri Oct 8 18:37:19 2010 +0200 - fixes diff --git a/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy b/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy index 9635eda..3d7811c 100644 --- a/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy +++ b/logback-classic/src/main/groovy/ch/qos/logback/classic/gaffer/GafferConfigurator.groovy @@ -21,7 +21,7 @@ class GafferConfigurator { LoggerContext context //ConfigurationDelegate configurationDelegate = new ConfigurationDelegate(); - + GafferConfigurator(LoggerContext context) { this.context = context //configurationDelegate.context = context; diff --git a/logback-site/src/site/pages/manual/jmxConfig.html b/logback-site/src/site/pages/manual/jmxConfig.html index 67ac974..7e7f7d9 100644 --- a/logback-site/src/site/pages/manual/jmxConfig.html +++ b/logback-site/src/site/pages/manual/jmxConfig.html @@ -50,13 +50,13 @@ <pre class="prettyprint source"><configuration> <jmxConfigurator /> - <appender name="console" class="ch.qos.logback.classic.ConsoleAppender"> + <appender name="console" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern>%date [%thread] %-5level %logger{25} - %msg%n</Pattern> </layout> </appender> - <root level="debug"/> + <root level="debug"> <appender-ref ref="console" /> </root> </configuration></pre> ----------------------------------------------------------------------- Summary of changes: .../classic/gaffer/GafferConfigurator.groovy | 2 +- logback-site/src/site/pages/manual/jmxConfig.html | 4 ++-- 2 files changed, 3 insertions(+), 3 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-21-gd52ee5d
by git-noreply＠pixie.qos.ch 05 Oct '10

05 Oct '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 d52ee5dcef840f3083950b0374bc5b06f9dfae97 (commit) from 090b95566ecbae1a3321bed43b1d9c15dcac32e8 (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=d52ee5dcef840f3083950b03… http://github.com/ceki/logback/commit/d52ee5dcef840f3083950b0374bc5b06f9dfa… commit d52ee5dcef840f3083950b0374bc5b06f9dfae97 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Tue Oct 5 20:48:39 2010 +0200 - typo fix diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 0755721..3944286 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -2669,14 +2669,14 @@ logger.error(notifyAdminMarker, MDCDiscriminator</a></h3> As mentioned earlier, by specifiying a discriminator other than - the default one, SMTPAppender will generate email messages - containing events pertaining to a particular user, user session or - client IP address, depending on the discriminator. + the default one, <code>SMTPAppender</code> will generate email + messages containing events pertaining to a particular user, user + session or client IP address, depending on the specified discriminator. - The next example uses <a - href="../xref/ch/qos/logback/classic/sift/MDCBasedDiscriminator.html">MDCBasedDsicriminator</a> - focused on the MDC key named "req.remoteHost" which is assumed to + The next example illustrates the use of<a + href="../xref/ch/qos/logback/classic/sift/MDCBasedDiscriminator.html">MDCBasedDiscriminator</a> + in conjuction with the MDC key named "req.remoteHost", assumed to contain the IP address of the remote host accessing a fictitious application. In a web-application, you could use <a href="mdc.html#mis">MDCInsertingServletFilter</a> to populate MDC ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

Missing logging of Throwable in SyslogAppender
by Tobias Lund-Melcher 05 Oct '10

05 Oct '10

Hi, the project I'm working on decided to switch to slf4j and logback for logging, and our experiences so far are very good. Thanks for the great work!! During implementation and testing we discovered that the SyslogAppender does not seem to log the throwable type and its message at all. To overcome this we've overridden the the SyslogAppender.postProcess() method. I believe this is a bug which should be addressed. The git diff after patching this is given below. Best Regards, Tobias Lund-Melcher -----------------git diff------------------------- diff --git a/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java b/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java index 67845db..bc35399 100644 --- a/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java +++ b/logback-classic/src/main/java/ch/qos/logback/classic/net/SyslogAppender.java @@ -21,6 +21,7 @@ import ch.qos.logback.classic.pattern.SyslogStartConverter; import ch.qos.logback.classic.spi.ILoggingEvent; import ch.qos.logback.classic.spi.IThrowableProxy; import ch.qos.logback.classic.spi.StackTraceElementProxy; +import ch.qos.logback.classic.spi.ThrowableProxyUtil; import ch.qos.logback.classic.util.LevelToSyslogSeverity; import ch.qos.logback.core.CoreConstants; import ch.qos.logback.core.Layout; @@ -82,10 +83,15 @@ public class SyslogAppender extends SyslogAppenderBase<ILoggingEvent> { IThrowableProxy tp = event.getThrowableProxy(); while (tp != null) { - StackTraceElementProxy[] stepArray = tp.getStackTraceElementProxyArray(); try { + StringBuilder sb = new StringBuilder(prefix); + ThrowableProxyUtil.printFirstLine(sb, tp); + sw.write(sb.toString().getBytes()); + sw.flush(); + + StackTraceElementProxy[] stepArray = tp.getStackTraceElementProxyArray(); for (StackTraceElementProxy step : stepArray) { - StringBuilder sb = new StringBuilder(); + sb = new StringBuilder(); sb.append(prefix).append(CoreConstants.TAB).append(step); sw.write(sb.toString().getBytes()); sw.flush(); diff --git a/logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java b/logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java index 83056a6..269f387 100644 --- a/logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java +++ b/logback-classic/src/test/java/ch/qos/logback/classic/net/SyslogAppenderTest.java @@ -132,6 +133,10 @@ public class SyslogAppenderTest { String regex = expectedPrefix + "\\[" + threadName + "\\] " + loggerName + " " + logMsg; checkRegexMatch(msg, regex); + + msg = mockServer.getMessageList().get(1); + assertTrue(msg.contains(ex.getClass().getName())); + assertTrue(msg.contains(ex.getMessage())); } private void checkRegexMatch(String s, String regex) {

1 0

[JIRA] Created: (LBCORE-117) Supply an appender that collects N events on all levels and dumps them to the output when an ERROR is logged
by Aaron Digulla (JIRA) 04 Oct '10

04 Oct '10

Supply an appender that collects N events on all levels and dumps them to the output when an ERROR is logged ------------------------------------------------------------------------------------------------------------ Key: LBCORE-117 URL: http://jira.qos.ch/browse/LBCORE-117 Project: logback-core Issue Type: New Feature Components: Appender Reporter: Aaron Digulla Assignee: Logback dev list For many applications, it's not necessary to log at the levels DEBUG and TRACE all the time. In fact, we usually only do this to be able to debug ERROR events. It would be great if there was an appender that would only collect a configurable number of events internally until a message of level ERROR or above is logged. At this time, the appender should dump it's internal state to the log and reset the internal state. -- 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

[GIT] Logback: the generic, reliable, fast and flexible logging framework. branch, master, updated. v_0.9.24-20-g090b955
by git-noreply＠pixie.qos.ch 30 Sep '10

30 Sep '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 090b95566ecbae1a3321bed43b1d9c15dcac32e8 (commit) from b100fbfa7db3cd43d4551bd70bb523a5c7543311 (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=090b95566ecbae1a3321bed4… http://github.com/ceki/logback/commit/090b95566ecbae1a3321bed43b1d9c15dcac3… commit 090b95566ecbae1a3321bed43b1d9c15dcac32e8 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 30 22:02:23 2010 +0200 typo fix diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index fe45f69..0755721 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -2142,7 +2142,7 @@ Context ctx = new InitialContext(env);</pre> The <a href="../xref/ch/qos/logback/classic/net/SMTPAppender.html"><code>SMTPAppender</code></a> accumulates logging events in one or more fixed-size buffers and - sends the contents of the appropriate bufferer in an email after a + sends the contents of the appropriate buffer in an email after a user-specified event occurs. By default, the email transmission is triggered by a logging event of level ERROR or higher. Moreover, by default, a single buffer is used for all events. ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 2 +- 1 files changed, 1 insertions(+), 1 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-19-gb100fbf
by git-noreply＠pixie.qos.ch 30 Sep '10

30 Sep '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 b100fbfa7db3cd43d4551bd70bb523a5c7543311 (commit) from 74915053db48b5e803816f8d39237cd85293273f (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=b100fbfa7db3cd43d4551bd7… http://github.com/ceki/logback/commit/b100fbfa7db3cd43d4551bd70bb523a5c7543… commit b100fbfa7db3cd43d4551bd70bb523a5c7543311 Author: Ceki Gulcu <ceki(a)qos.ch> Date: Thu Sep 30 21:58:31 2010 +0200 - Many editorial fixes submitted by Dan Lantz. diff --git a/logback-site/src/site/pages/manual/appenders.html b/logback-site/src/site/pages/manual/appenders.html index 6196232..fe45f69 100644 --- a/logback-site/src/site/pages/manual/appenders.html +++ b/logback-site/src/site/pages/manual/appenders.html @@ -65,7 +65,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl }</pre> Most of the methods in the <code>Appender</code> interface are - made of setter and getter methods. A notable exception is the + setters and getters. A notable exception is the <code>doAppend()</code> method taking an object instance of type E as its only parameter. The actual type of E would vary depending on the logback module. Within the @@ -300,8 +300,8 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl <code>ConsoleAppender</code></a>, as the name indicates, appends on the console, or more precisely on System.out or System.err, the former being the default - target. <code>ConsoleAppender</code> formats events with the hellp - of an encoder specified by the user. Encoders will be discussed in a + target. <code>ConsoleAppender</code> formats events with the help of + an encoder specified by the user. Encoders will be discussed in a subsequent chapter. Both System.out and System.err are of type <code>java.io.PrintStream</code>. Consequently, they are wrapped inside an <code>OutputStreamWriter</code> which buffers @@ -586,8 +586,7 @@ public interface Appender<E> extends LifeCycle, ContextAware, FilterAttachabl below</a>) will determine if and exactly when rollover occurs. Thus, <code>RollingPolicy</code> is responsible for the what and <code>TriggeringPolicy</code> is responsible for - the when. <code>RollingPolicy</code> is described - + the when. To be of any use, a <code>RollingFileAppender</code> must have both a <code>RollingPolicy</code> and a @@ -906,9 +905,10 @@ public interface RollingPolicy extends LifeCycle { interfaces. - <code>TimeBasedRollingPolicy</code>'s admits two properties, the - mandatory fileNamePattern property and - the optional maxHistory property. + <code>TimeBasedRollingPolicy</code>'s configuration admits two + properties, the mandatory fileNamePattern property and the optional + maxHistory property. <table class="bodyTable"> @@ -2142,7 +2142,7 @@ Context ctx = new InitialContext(env);</pre> The <a href="../xref/ch/qos/logback/classic/net/SMTPAppender.html"><code>SMTPAppender</code></a> accumulates logging events in one or more fixed-size buffers and - sends the contents of the appropriate bugger in an email after a + sends the contents of the appropriate bufferer in an email after a user-specified event occurs. By default, the email transmission is triggered by a logging event of level ERROR or higher. Moreover, by default, a single buffer is used for all events. diff --git a/logback-site/src/site/pages/manual/architecture.html b/logback-site/src/site/pages/manual/architecture.html index 3af7059..b4a5841 100644 --- a/logback-site/src/site/pages/manual/architecture.html +++ b/logback-site/src/site/pages/manual/architecture.html @@ -745,11 +745,11 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> <h4>1. Get the filter chain decision</h4> If it exists, the <code>TurboFilter</code> chain is - invoked. Turbo filters can set a context-wide threshold, or to - filter out certain events based on information such as - <code>Marker</code>, <code>Level</code>, <code>Logger</code>, - message, or the <code>Throwable</code> that are associated with each - logging request. If the reply of the filter chain is + invoked. Turbo filters can set a context-wide threshold, or filter + out certain events based on information such as <code>Marker</code>, + <code>Level</code>, <code>Logger</code>, message, or the + <code>Throwable</code> that are associated with each logging + request. If the reply of the filter chain is <code>FilterReply.DENY</code>, then the logging request is dropped. If it is <code>FilterReply.NEUTRAL</code>, then we continue with the next step, i.e. step 2. In case the reply is @@ -880,12 +880,12 @@ logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre> and 4 microseconds to format a message with 1 and 3 parameters. - Please notice that, despite the performance points that we just - discussed, inserting logging statements in tight loops or very - frequently invoked code is a lose-lose proposal and is likely to - result in degraded performance. Logging in tight loops slow down - your application even if logging is turned off, and if logging is - turned on, they will generate massive (and hence useless) output. + Please notice that, despite the performance points just + discussed, inserting logging statements in tight loops (very + frequently invoked code) is a lose-lose proposal and is likely to + result in degraded performance. Logging in tight loops will slow + down your application even if logging is turned off, and if logging + is turned on, will generate massive (and hence useless) output. <h4>2. The performance of deciding whether to log or not to log when diff --git a/logback-site/src/site/pages/manual/configuration.html b/logback-site/src/site/pages/manual/configuration.html index 769d170..9782baf 100644 --- a/logback-site/src/site/pages/manual/configuration.html +++ b/logback-site/src/site/pages/manual/configuration.html @@ -218,7 +218,7 @@ public class Foo { </div> The <code>MyApp1</code> application links to logback via calls - <code>org.slf4j.LoggerFactory</code> and + to <code>org.slf4j.LoggerFactory</code> and <code>org.slf4j.Logger</code> classes, retrieve the loggers it wishes to use, and chugs on. Note that the only dependencies of the <code>Foo</code> class on logback are through @@ -527,7 +527,7 @@ public class MyApp3 { currently in effect, creates a new <code>JoranConfigurator</code>, sets the context on which it will operate, resets the logger context, and then finally asks the configurator to configure the - context using configuration file passed as parameter to the + context using the configuration file passed as a parameter to the application. Internal status data is printed in case of warnings or errors. @@ -547,7 +547,7 @@ public class MyApp3 { data associated with a logback context. To keep memory usage at reasonable levels, the default <code>StatusManager</code> implementation stores the status messages in two separate parts: - the header part and the tail part. The header part stores the fist + the header part and the tail part. The header part stores the first H status messages whereas the tail part stores the last T messages. At present time H=T=150, although these values may change in future releases. @@ -709,12 +709,12 @@ public class MyApp3 { href="#loggerElement">Configuring loggers, or the <code><logger></code> element</a></h4> - At this point should have at least some understanding of <a + At this point you should have at least some understanding of <a 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 - are hieroglyphics. + configuration will be no more meaningful to you than are + hieroglyphics. A logger is configured using the <code><logger></code> @@ -893,7 +893,7 @@ public class MyApp3 { Let us note that the <a href="architecture.html#basic_selection">basic-selection rule</a> depends on the effective level of the logger being invoked, not the - level of the logger where appenders are attached. Loback will first + level of the logger where appenders are attached. Logback will first determine whether a logging statement is enabled or not, and if enabled, it will invoke the appenders found in the logger hierarchy, regardless of their level. The configuration file @@ -976,7 +976,7 @@ public class MyApp3 { <h4><a name="configuringAppenders" href="#configuringAppenders">Configuring Appenders</a></h4> - An appenders is configured with the <code><appender></code> + An appender is configured with the <code><appender></code> element, which takes two mandatory attributes name and class. The name attribute specifies the name of the @@ -1051,7 +1051,7 @@ public class MyApp3 { </root> </configuration></pre> - This configuration scripts defines two appenders called + These configuration scripts define two appenders called FILE and STDOUT. The FILE appender logs to a file called myApp.log. The encoder for this appender is a <code>PatternLayoutEncoder</code> that outputs the date, level, @@ -1113,12 +1113,14 @@ public class MyApp3 { 14:25:36.359 [main] INFO chapters.configuration.MyApp3 - Exiting application. Notice the duplicated output. The appender named STDOUT - is attached to two loggers, to root and to chapters.configuration. Since - the root logger is the ancestor of all loggers and chapters.configuration - is the parent of chapters.configuration.MyApp3 and chapters.configuration.Foo, - logging request made with these two loggers will be output twice, - once because STDOUT is attached to chapters.configuration and - once because it is attached to root. + is attached to two loggers, to root and to + chapters.configuration. Since the root logger is the + ancestor of all loggers and chapters.configuration is the + parent of both chapters.configuration.MyApp3 and + chapters.configuration.Foo, each logging request made with + these two loggers will be output twice, once because STDOUT + is attached to chapters.configuration and once because it + is attached to root. Appender additivity is not intended as a trap for new users. It @@ -1219,10 +1221,10 @@ public class MyApp3 { <h3><a name="contextName" href="#contextName">Setting the context name</a></h3> As mentioned <a href="architecture.html#LoggerContext">in an - earlier chapter</a>, every logger is attached to logger context. By - default, the logger context is called "default". However, you can - set a different name with the help of the - <code><contextName></code> configuration directive. Note that + earlier chapter</a>, every logger is attached to a logger + context. By default, the logger context is called + "default". However, you can set a different name with the help of + the <code><contextName></code> configuration directive. Note that once set, the logger context name <a href="../apidocs/ch/qos/logback/core/ContextBase.html#setName(java.lang.String)">cannot be changed</a>. Setting the context name is a simple and @@ -1247,8 +1249,8 @@ public class MyApp3 { </root> </configuration></pre> - This last examples illustrates naming of the logger - context. Adding the the <a + This last example illustrates naming of the logger + context. Adding the <a href="layouts.html#conversionWord">contextName conversion word</a> in layout's pattern will output the said name. @@ -1363,9 +1365,9 @@ public class MyApp3 { This configuration file contains a reference to a file named variables1.properties. The variables contained in that - file will be read defined within the context of the logback - configuration file. Here is what the variable.properties - file might look like. + file will be read and then defined within the context of the + logback configuration file. Here is what the + variable.properties file might look like. Example: Variable file @@ -1598,7 +1600,7 @@ fileName=myApp.log Under certain circumstances, you may want to make use of env-entries stored in JNDI. The <code><insertFromJNDI></code> configuration directive extracts an env-entry stored in JNDI and - inserts it as variable as specified by the as attribute. diff --git a/logback-site/src/site/pages/manual/introduction.html b/logback-site/src/site/pages/manual/introduction.html index 1e10a0f..481d609 100644 --- a/logback-site/src/site/pages/manual/introduction.html +++ b/logback-site/src/site/pages/manual/introduction.html @@ -50,7 +50,7 @@ existing logging systems, sometimes by a wide margin. Logback also offers unique and rather useful features such as Markers, parameterized logging statements, conditional stack tracing and - powerful event filtering. These are only few examples of useful + powerful event filtering. These are only a few examples of useful features logback has to offer. For its own error reporting, logback relies on <code>Status</code> objects, which greatly facilitate troubleshooting. You may wish to rely on Status objects @@ -220,7 +220,7 @@ public class HelloWorld2 { or the class itself as a parameter.</li> <li>Use this logger instance by invoking its printing methods, - namely the debug(), info(), warn() and error(). This will + namely the debug(), info(), warn() and error() methods. This will produce logging output on the configured appenders.</li> </ol> ----------------------------------------------------------------------- Summary of changes: logback-site/src/site/pages/manual/appenders.html | 18 +++--- .../src/site/pages/manual/architecture.html | 22 ++++---- .../src/site/pages/manual/configuration.html | 52 ++++++++++--------- .../src/site/pages/manual/introduction.html | 4 +- 4 files changed, 49 insertions(+), 47 deletions(-) hooks/post-receive -- Logback: the generic, reliable, fast and flexible logging framework.

1 0

[JIRA] Created: (LBCORE-167) An exception is thrown during the web application startup.
by Pavel Mikhalchuk (JIRA) 17 Sep '10

17 Sep '10

An exception is thrown during the web application startup. ---------------------------------------------------------- Key: LBCORE-167 URL: http://jira.qos.ch/browse/LBCORE-167 Project: logback-core Issue Type: Bug Components: Appender Affects Versions: 0.9.24 Environment: Ubuntu 9.04 Reporter: Pavel Mikhalchuk Assignee: Logback dev list Appender is configurated the next way: <appender name="appender class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>some_host</SMTPHost> <BufferSize>10</BufferSize> <To>some(a)email.address</To> <From>som(a)email.address2</From> <Subject>Some subject</Subject> <layout class="ch.qos.logback.classic.html.HTMLLayout"/> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>Some Marker</marker> </evaluator> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="MARKER"> <expression>marker != null && event.getLevel().toInt() >= WARN</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> And when the web application is starting the following stacktrace can be observed: 21:02:57,596 |-ERROR in ch.qos.logback.classic.boolex.JaninoEventEvaluator@1bde392 - Could not start evaluator with expression [marker != null && event.getLevel().toInt() >= WARN.toInt()] org.codehaus.janino.CompileException: Line 2, Column 57: A method named "toInt" is not declared in any enclosing class nor any supertype, nor through a static import at org.codehaus.janino.CompileException: Line 2, Column 57: A method named "toInt" is not declared in any enclosing class nor any supertype, nor through a static import at at org.codehaus.janino.UnitCompiler.compileError(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.findIMethod(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$51(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$9.visitMethodInvocation(UnitCompiler.java) at at org.codehaus.janino.Java$MethodInvocation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileGet(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGetValue(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileBoolean2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$31(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$7.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileBoolean(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileBoolean2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$31(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$7.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileBoolean(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGet2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$44(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$9.visitBinaryOperation(UnitCompiler.java) at at org.codehaus.janino.Java$BinaryOperation.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compileGet(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileGetValue(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$17(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$4.visitReturnStatement(UnitCompiler.java) at at org.codehaus.janino.Java$ReturnStatement.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.access$7(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$4.visitBlock(UnitCompiler.java) at at org.codehaus.janino.Java$Block.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compile2(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler$3.visitPackageMemberClassDeclaration(UnitCompiler.java) at at org.codehaus.janino.Java$PackageMemberClassDeclaration.accept(Java.java) at at org.codehaus.janino.UnitCompiler.compile(UnitCompiler.java) at at org.codehaus.janino.UnitCompiler.compileUnit(UnitCompiler.java) at at org.codehaus.janino.SimpleCompiler.compileToClassLoader(SimpleCompiler.java) at at org.codehaus.janino.ClassBodyEvaluator.compileToClass(ClassBodyEvaluator.java) at at org.codehaus.janino.ScriptEvaluator.cook(ScriptEvaluator.java) at at org.codehaus.janino.ScriptEvaluator.cook(ScriptEvaluator.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.Cookable.cook(Cookable.java) at at org.codehaus.janino.ExpressionEvaluator.<init>(ExpressionEvaluator.java) at at ch.qos.logback.core.boolex.JaninoEventEvaluatorBase.start(JaninoEventEvaluatorBase.java:58) at at ch.qos.logback.core.joran.action.NestedComplexPropertyIA.end(NestedComplexPropertyIA.java:168) at at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:315) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:194) at at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:180) at at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:52) at at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:332) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:126) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:93) at at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:52) at at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:77) at at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:150) at at org.slf4j.impl.StaticLoggerBinder.init(StaticLoggerBinder.java:85) at at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:55) at at org.slf4j.LoggerFactory.bind(LoggerFactory.java:121) at at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:111) at at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:268) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:241) at at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:254) at at com.shc.obu.mp.sellpo.batch.ContextListener.<clinit>(ContextListener.java:13) at at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at at java.lang.Class.newInstance0(Class.java:355) at at java.lang.Class.newInstance(Class.java:308) at at org.mortbay.jetty.webapp.WebXmlConfiguration.newListenerInstance(WebXmlConfiguration.java:650) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initListener(WebXmlConfiguration.java:631) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initWebXmlElement(WebXmlConfiguration.java:368) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initWebXmlElement(AbstractConfiguration.java:190) at at org.mortbay.jetty.webapp.WebXmlConfiguration.initialize(WebXmlConfiguration.java:289) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.initialize(AbstractConfiguration.java:133) at at org.mortbay.jetty.webapp.WebXmlConfiguration.configure(WebXmlConfiguration.java:222) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configure(AbstractConfiguration.java:113) at at org.mortbay.jetty.webapp.WebXmlConfiguration.configureWebApp(WebXmlConfiguration.java:180) at at org.mortbay.jetty.plus.webapp.AbstractConfiguration.configureWebApp(AbstractConfiguration.java:96) at at org.mortbay.jetty.plus.webapp.Configuration.configureWebApp(Configuration.java:149) at at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1247) at at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517) at at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467) at at org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130) at at org.mortbay.jetty.Server.doStart(Server.java:224) at at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50) at at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:132) at at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:441) at at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:383) at at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:210) at at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:184) at at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at at java.lang.reflect.Method.invoke(Method.java:597) at at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at at org.codehaus.classworlds.Launcher.main(Launcher.java:375) at at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at at java.lang.reflect.Method.invoke(Method.java:597) at at com.intellij.rt.execution.application.AppMain.main(AppMain.java:110) The only one right configuration without exceptions is: <appender name="appender class="ch.qos.logback.classic.net.SMTPAppender"> <SMTPHost>some_host</SMTPHost> <BufferSize>10</BufferSize> <To>some(a)email.address</To> <From>som(a)email.address2</From> <Subject>Some subject</Subject> <layout class="ch.qos.logback.classic.html.HTMLLayout"/> <evaluator class="ch.qos.logback.classic.boolex.OnMarkerEvaluator"> <marker>Some Marker</marker> </evaluator> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="MARKER"> <expression>marker != null && event.getLevel().toInt() >= WARN</expression> </evaluator> <OnMatch>ACCEPT</OnMatch> <OnMismatch>DENY</OnMismatch> </filter> </appender> event.getLevel().toInt() >= WARN (not event.getLevel().toInt() >= WARN.toInt()) But according to http://logback.qos.ch/manual/filters.html#evalutatorFilter we need to use event.getLevel().toInt() >= WARN.toInt(). -- 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 3