- logback-dev - mailman3.qos.ch

[Bug 146] New: LoggerContext.getLogger(final String name) doesn't check if name is null
by bugzilla-daemon＠pixie.qos.ch 12 Apr '08

12 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=146 Summary: LoggerContext.getLogger(final String name) doesn't check if name is null Product: logback-classic Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: info(a)oliverlietz.de hence loggerCache.get(name) could fail (NPE) in line 117: java.lang.NullPointerException at java.util.Hashtable.get(Hashtable.java:336) at ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:117) at ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:44) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:88) at org.apache.sling.osgi.log.LogSupport.getLogger(LogSupport.java:322) at org.apache.sling.osgi.log.LogSupport.logOut(LogSupport.java:333) at org.apache.sling.osgi.log.LogSupport.fireLogEvent(LogSupport.java:167) at org.apache.sling.osgi.log.LogSupport.bundleChanged(LogSupport.java:216) at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:690) at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:619) at org.apache.felix.framework.util.EventDispatcher.run(EventDispatcher.java:816) at org.apache.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:42) at org.apache.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:94) at java.lang.Thread.run(Thread.java:613) -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 0

svn commit: r1671 - in logback/trunk: logback-examples/src/main/java/chapter7 logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 11 Apr '08

11 Apr '08

Author: ceki Date: Sat Apr 12 01:18:33 2008 New Revision: 1671 Modified: logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java logback/trunk/logback-site/src/site/pages/manual/mdc.html Log: - correcting documentation and SimpleMDC code, in light of problems reported [1] on the logback mailing list by Daniel King [1] http://www.qos.ch/pipermail/logback-user/2008-April/000427.html Modified: logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java ============================================================================== --- logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java (original) +++ logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java Sat Apr 12 01:18:33 2008 @@ -10,36 +10,37 @@ package chapter7; +import java.net.URL; + import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.slf4j.MDC; +import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.PatternLayout; +import ch.qos.logback.classic.joran.JoranConfigurator; import ch.qos.logback.classic.spi.LoggingEvent; import ch.qos.logback.core.ConsoleAppender; +import ch.qos.logback.core.joran.spi.JoranException; +import ch.qos.logback.core.util.Loader; +import ch.qos.logback.core.util.StatusPrinter; public class SimpleMDC { static public void main(String[] args) throws Exception { - // You can put values in the MDC at any time. We first put the - // first name + // You can put values in the MDC at any time. Before anything else + // we put the first name MDC.put("first", "Dorothy"); - // Configure logback - PatternLayout layout = new PatternLayout(); - layout.setPattern("%X{first} %X{last} - %m%n"); - layout.start(); - ConsoleAppender<LoggingEvent> appender = new ConsoleAppender<LoggingEvent>(); - appender.setLayout(layout); - appender.start(); - // cast root logger to c.q.logback.classic.Logger so that we can attach an - // appender to it - ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory - .getLogger("root"); - root.addAppender(appender); - - // get another logger + // configure via the configuration file "chapter7/simpleMDC.xml" + // which ships with the examples + configureViaXML_File(); + + // For educational purposes, the same configuration can + // be accomplished programmatically. + // + // programmaticConfiguration(); + Logger logger = LoggerFactory.getLogger(SimpleMDC.class); - // We now put the last name MDC.put("last", "Parker"); @@ -53,4 +54,38 @@ logger.info("I am not a crook."); logger.info("Attributed to the former US president. 17 Nov 1973."); } + + static void programmaticConfiguration() { + // Configure logback + LoggerContext loggerContext = (LoggerContext) LoggerFactory + .getILoggerFactory(); + loggerContext.shutdownAndReset(); + PatternLayout layout = new PatternLayout(); + layout.setContext(loggerContext); + layout.setPattern("%X{first} %X{last} - %m%n"); + layout.start(); + ConsoleAppender<LoggingEvent> appender = new ConsoleAppender<LoggingEvent>(); + appender.setContext(loggerContext); + appender.setLayout(layout); + appender.start(); + // cast root logger to c.q.logback.classic.Logger so that we can attach + // an appender to it + ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory + .getLogger("root"); + root.addAppender(appender); + } + + static void configureViaXML_File() { + LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); + try { + JoranConfigurator configurator = new JoranConfigurator(); + configurator.setContext(lc); + lc.shutdownAndReset(); + URL url = Loader.getResourceByTCL("chapter7/simpleMDC.xml"); + configurator.doConfigure(url); + } catch (JoranException je) { + StatusPrinter.print(lc); + } + } + } Modified: logback/trunk/logback-site/src/site/pages/manual/mdc.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/mdc.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/mdc.html Sat Apr 12 01:18:33 2008 @@ -112,29 +112,16 @@ public class SimpleMDC { static public void main(String[] args) throws Exception { - // You can put values in the MDC at any time. We first put the - // first name - <b>MDC.put("first", "Dorothy");</b> - - // Configure logback - PatternLayout layout = new PatternLayout(); - layout.setPattern("%X{first} %X{last} - %m%n"); - layout.start(); - ConsoleAppender<LoggingEvent> appender = new ConsoleAppender<LoggingEvent>(); - appender.setLayout(layout); - appender.start(); - - // cast root logger to c.q.logback.classic.Logger so that we can attach an - // appender to it - ch.qos.logback.classic.Logger root = (ch.qos.logback.classic.Logger) LoggerFactory - .getLogger("root"); - root.addAppender(appender); - // get another logger - Logger logger = (Logger)LoggerFactory.getLogger(SimpleMDC.class); + // You can put values in the MDC at any time. Before anything else + // we put the first name + MDC.put("first", "Dorothy"); + [ SNIP ] + + Logger logger = LoggerFactory.getLogger(SimpleMDC.class); // We now put the last name - <b>MDC.put("last", "Parker");</b> + MDC.put("last", "Parker"); // The most beautiful two words in the English language according // to Dorothy Parker: @@ -146,22 +133,42 @@ logger.info("I am not a crook."); logger.info("Attributed to the former US president. 17 Nov 1973."); } + + [ SNIP ] + }</pre></div> - <p> - The main method starts by associating the value <em>Dorothy</em> with - the key <em>first</em> in the <code>MDC</code>. You can place as many - value/key associations in the <code>MDC</code> as you wish. - Multiple insertions with the same key will overwrite older values. - The code then proceeds to configure logback. - Note the usage of the <em>%X</em> specifier within the - <code>PatternLayout</code> conversion pattern. The <em>%X</em> - conversion specifier is employed twice, once for the key <em>first</em> - and once for the key <em>last</em>. After configuring the root logger, - the code associates the value <em>Parker</em> with the key <em>last</em>. - It then invokes the logger twice with different messages. - The code finishes by setting the <code>MDC</code> to different values - and issuing several logging requests. Running SimpleMDC yields: + <p>The main method starts by associating the value + <em>Dorothy</em> with the key <em>first</em> in the + <code>MDC</code>. You can place as many value/key associations in + the <code>MDC</code> as you wish. Multiple insertions with the + same key will overwrite older values. The code then proceeds to + configure logback.</p> + + <p>For the sake of consiceness, we have the omitted the code that + configures logback with the configuration file <a + href="http://tinyurl.com/4gy542">simpleMDC.xml</a>. Here is the + relevant section from that file. + </p> + + <p class="source"><appender name="CONSOLE" + class="ch.qos.logback.core.ConsoleAppender"> <layout + class="ch.qos.logback.classic.PatternLayout"> + <Pattern><b>%X{first} %X{last}</b> - %m%n</Pattern> + </layout> </appender></p> + + + + <p>Note the usage of the <em>%X</em> specifier within the + <code>PatternLayout</code> conversion pattern. The <em>%X</em> + conversion specifier is employed twice, once for the key named + <em>first</em> and once for the key named <em>last</em>. After + obtaining a logger corresponding to <code>SimpleMDC.class</code>, + the code associates the value <em>Parker</em> with the key named + <em>last</em>. It then invokes the logger twice with different + messages. The code finishes by setting the <code>MDC</code> to + different values and issuing several logging requests. Running + SimpleMDC yields: </p> <div class="source"><pre>Dorothy Parker - Check enclosed. @@ -170,11 +177,11 @@ Richard Nixon - Attributed to the former US president. 17 Nov 1973.</pre></div> - <p> - The <code>SimpleMDC</code> application illustrates how logback layouts, - if configured appropriately, automatically output <code>MDC</code> information. - Moreover, the information placed into the <code>MDC</code> can be used by - multiple logger invocations. + <p>The <code>SimpleMDC</code> application illustrates how logback + layouts, if configured appropriately, can automatically output + <code>MDC</code> information. Moreover, the information placed + into the <code>MDC</code> can be used by multiple logger + invocations. </p> <h3>Advanced Use</h3>

1 0

svn commit: r1670 - logback/trunk/logback-examples/src/main/java/chapter7
by noreply.ceki＠qos.ch 11 Apr '08

11 Apr '08

Author: ceki Date: Sat Apr 12 01:08:27 2008 New Revision: 1670 Added: logback/trunk/logback-examples/src/main/java/chapter7/simpleMDC.xml Log: - Express the configuration done by SimpleMDC.java in a config file Added: logback/trunk/logback-examples/src/main/java/chapter7/simpleMDC.xml ============================================================================== --- (empty file) +++ logback/trunk/logback-examples/src/main/java/chapter7/simpleMDC.xml Sat Apr 12 01:08:27 2008 @@ -0,0 +1,16 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<configuration> + + <appender name="CONSOLE" + class="ch.qos.logback.core.ConsoleAppender"> + <layout class="ch.qos.logback.classic.PatternLayout"> + <Pattern>%X{first} %X{last} - %m%n</Pattern> + </layout> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="CONSOLE" /> + </root> +</configuration>

1 0

svn commit: r1669 - logback/trunk/logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 11 Apr '08

11 Apr '08

Author: ceki Date: Fri Apr 11 23:29:32 2008 New Revision: 1669 Modified: logback/trunk/logback-site/src/site/pages/manual/mdc.html Log: - added missing import Modified: logback/trunk/logback-site/src/site/pages/manual/mdc.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/mdc.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/mdc.html Fri Apr 11 23:29:32 2008 @@ -107,6 +107,7 @@ import org.slf4j.MDC; import ch.qos.logback.classic.PatternLayout; +import ch.qos.logback.classic.spi.LoggingEvent; import ch.qos.logback.core.ConsoleAppender; public class SimpleMDC {

1 0

svn commit: r1668 - in logback/trunk: . logback-site/src/site/pages
by noreply.ceki＠qos.ch 08 Apr '08

08 Apr '08

Author: ceki Date: Tue Apr 8 11:16:32 2008 New Revision: 1668 Modified: logback/trunk/LICENSE.txt logback/trunk/logback-site/src/site/pages/license.html Log: - subsequent to discussions on the mailing list, tentatively changing the license to GPL+classpath exception instead of the less clear LGPL+classpath. Note that GPL+classpath is the same license terms as JDK 7. Modified: logback/trunk/LICENSE.txt ============================================================================== --- logback/trunk/LICENSE.txt (original) +++ logback/trunk/LICENSE.txt Tue Apr 8 11:16:32 2008 @@ -1,13 +1,40 @@ Logback LICENSE ---------------------------- +--------------- -Logback source code and binaries are distributed under the -GNU Lesser General Public License as published by the Free Software Foundation. +Logback: the reliable, generic, fast and flexible logging library for +Java. -Logback: the generic, reliable, fast and flexible logging library for Java. +Copyright (C) 2000-2008, QOS.ch + +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or (at +your option) any later version. + +This program is distributed in the hope that it will be useful, but +WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU +General Public License for more details. + + +CLASSPATH EXCEPTION TO THE GPL + +Linking this library statically or dynamically with other modules is +making a combined work based on this library. Thus, the terms and +conditions of the GNU General Public License cover the whole +combination. + +As a special exception, the copyright holders of this library give you +permission to link this library with independent modules to produce an +executable, regardless of the license terms of these independent +modules, and to copy and distribute the resulting executable under +terms of your choice, provided that you also meet, for each linked +independent module, the terms and conditions of the license of that +module. An independent module is a module which is not derived from or +based on this library. If you modify this library, you may extend +this exception to your version of the library, but you are not obliged +to do so. If you do not wish to do so, delete this exception statement +from your version. -Copyright (C) 2000-2006, QOS.ch This library is free software, you can -redistribute it and/or modify it under the terms of the GNU Lesser General Public License -as published by the Free Software Foundation. Modified: logback/trunk/logback-site/src/site/pages/license.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/license.html (original) +++ logback/trunk/logback-site/src/site/pages/license.html Tue Apr 8 11:16:32 2008 @@ -24,23 +24,30 @@ </div> <p>Logback source code and binaries are distributed under the <a - href="http://www.gnu.org/licenses/lgpl.html">GNU Lesser General - Public License</a> as published by the Free Software Foundation. + href="http://www.gnu.org/licenses/gpl-2.0.html">GNU General Public + License version 2</a> as published by the Free Software Foundation. </p> <div class="source"><pre>Logback: the reliable, generic, fast and flexible logging library for Java. -Copyright (C) 2000-2006, QOS.ch +Copyright (C) 2000-2008, QOS.ch -This library is free software, you can redistribute it and/or modify -it under the terms of the GNU Lesser General Public License as -published by the Free Software Foundation.</pre></div> +This program is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software Foundation; either version 2 of the License, or (at +your option) any later version. + +This program is distributed in the hope that it will be useful, +but WITHOUT ANY WARRANTY; without even the implied warranty of +MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +GNU General Public License for more details. +</pre></div>  <p>Logback will remain an open-source project distributed under the -LGPL for the foreseeable future -- foreseeable as in the future you -can reasonably think or talk about. In other words, there are no plans +GPL for the foreseeable future -- foreseeable as in the future you can +reasonably think or talk about. In other words, there are no plans whatsoever to make logback a commercial project. </p> @@ -58,29 +65,25 @@ <h3>Classpath Exception</h3> -<p>According to the terms of LGPL, a "Combined Work" is a work -produced by combining or linking an Application with logback (the -Library). In section 4, the LGPL mandates that one may convey a -Combined Work under terms of one's choice that, taken together, -effectively do not restrict modification of the portions of the -Library contained in the Combined Work and reverse engineering for -debugging such modifications. +<p>Linking this library statically or dynamically with other modules +is making a combined work based on this library. Thus, the terms and +conditions of the GNU General Public License cover the whole +combination. </p> -<p>As a special exception, the copyright holders of logback give you -permission to link logback with independent modules to produce an -executable, regardless of the license terms of these independent -modules, and to copy and distribute the resulting executable under -terms of your choice, provided that you also meet, for each linked -independent module, the terms and conditions of the license of that -module. An independent module is a module which is not derived from or -based on logback. If you modify logback, you may extend this exception -to your version of logback, but you are not obliged to do so. If you -do not wish to do so, delete this exception statement from your -version. +<p>As a special exception, the copyright holders of this library give +you permission to link this library with independent modules to +produce an executable, regardless of the license terms of these +independent modules, and to copy and distribute the resulting +executable under terms of your choice, provided that you also meet, +for each linked independent module, the terms and conditions of the +license of that module. An independent module is a module which is not +derived from or based on this library. If you modify this library, you +may extend this exception to your version of the library, but you are +not obliged to do so. If you do not wish to do so, delete this +exception statement from your version. </p> - <script src="templates/footer.js"></script> </div>

1 0

svn commit: r1667 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 07 Apr '08

07 Apr '08

Author: ceki Date: Mon Apr 7 22:28:13 2008 New Revision: 1667 Modified: logback/trunk/logback-site/src/site/pages/license.html Log: - tentatively adding the "Classpath exception" pending further discussion Modified: logback/trunk/logback-site/src/site/pages/license.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/license.html (original) +++ logback/trunk/logback-site/src/site/pages/license.html Mon Apr 7 22:28:13 2008 @@ -19,19 +19,16 @@ </div> <div id="content"> - <div class="section"> - <h2>Logback License</h2> - </div> - - <p> - Logback source code and binaries are distributed under the - <a href="http://www.gnu.org/licenses/lgpl.html"> - GNU Lesser General Public License - </a> - as published by the Free Software Foundation. - </p> + <div class="section"> + <h2>Logback License</h2> + </div> + + <p>Logback source code and binaries are distributed under the <a + href="http://www.gnu.org/licenses/lgpl.html">GNU Lesser General + Public License</a> as published by the Free Software Foundation. + </p> - <div class="source big"><pre>Logback: the reliable, generic, fast and flexible logging library for Java. + <div class="source"><pre>Logback: the reliable, generic, fast and flexible logging library for Java. Copyright (C) 2000-2006, QOS.ch @@ -39,21 +36,51 @@ it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation.</pre></div> - <p>Please note that logback is intended to be used behind the - SLF4J API, which is licensed under <a - href="http://www.slf4j.org/license.html">an X11 type license</a>. - </p> - - <p>If you wish to make a significant contribution to the logback - project, we invite you to file <a href="cla.txt">Contributor - License Agreement</a>. The purpose of this agreement is to - formalize the terms of your contribution and to protect the - project in case of litigation. - </p> + + +<p>Logback will remain an open-source project distributed under the +LGPL for the foreseeable future -- foreseeable as in the future you +can reasonably think or talk about. In other words, there are no plans +whatsoever to make logback a commercial project. +</p> + +<p>Please note that logback is intended to be used behind the SLF4J +API, which is licensed under <a +href="http://www.slf4j.org/license.html">an X11 type license</a>. +</p> + +<p>If you wish to make a significant contribution to the logback +project, we invite you to file <a href="cla.txt">Contributor License +Agreement</a>. The purpose of this agreement is to formalize the terms +of your contribution and to protect the project in case of litigation. +</p> + + +<h3>Classpath Exception</h3> + +<p>According to the terms of LGPL, a "Combined Work" is a work +produced by combining or linking an Application with logback (the +Library). In section 4, the LGPL mandates that one may convey a +Combined Work under terms of one's choice that, taken together, +effectively do not restrict modification of the portions of the +Library contained in the Combined Work and reverse engineering for +debugging such modifications. +</p> + +<p>As a special exception, the copyright holders of logback give you +permission to link logback with independent modules to produce an +executable, regardless of the license terms of these independent +modules, and to copy and distribute the resulting executable under +terms of your choice, provided that you also meet, for each linked +independent module, the terms and conditions of the license of that +module. An independent module is a module which is not derived from or +based on logback. If you modify logback, you may extend this exception +to your version of logback, but you are not obliged to do so. If you +do not wish to do so, delete this exception statement from your +version. +</p> + - - - <script src="templates/footer.js"></script> </div>

1 0

[Bug 107] New: Specificy the config file to use as a System property
by bugzilla-daemon＠pixie.qos.ch 04 Apr '08

04 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=107 Summary: Specificy the config file to use as a System property Product: logback-core Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: tgraham(a)concordenergy.com I'd like to be able to specify the logger config file to use as a System property, something like: java -Dlogback.configuration=customConfig.xml This is a much cleaner way of controlling the config than by messing with the classpath. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 6

[Bug 144] New: JMS Appender Fails - Odd Interaction with Commons Logging
by bugzilla-daemon＠pixie.qos.ch 04 Apr '08

04 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=144 Summary: JMS Appender Fails - Odd Interaction with Commons Logging Product: logback-core Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: blocker Priority: P1 Component: Appender AssignedTo: logback-dev(a)qos.ch ReportedBy: torr0101(a)gmail.com I'm not sure exactly what's going on, but I've been able to determine that the JMS appender doesn't work under certain circumstances due to some interaction with commons logging. Here is my maven POM: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>foo.bar</groupId> <artifactId>testbed</artifactId> <name>Testbed</name> <packaging>jar</packaging> <version>0.1-SNAPSHOT</version> <build> <plugins> <plugin> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-core</artifactId> <version>5.0.0</version> <exclusions> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging</artifactId> </exclusion> <exclusion> <groupId>commons-logging</groupId> <artifactId>commons-logging-api</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.4.3</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>jcl104-over-slf4j</artifactId> <version>1.4.3</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> <version>0.9.9</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>0.9.9</version> </dependency> </dependencies> </project> Here is my logback config: <configuration debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n </Pattern> </layout> </appender>  <root> <level value="TRACE" /> <appender-ref ref="STDOUT" /> </root> </configuration> Uncommenting the QUEUE appender results in the following stack trace: Failed to instantiate [ch.qos.logback.classic.LoggerContext] Reported exception: java.lang.ExceptionInInitializerError at org.apache.activemq.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:88) at org.apache.activemq.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:121) at org.apache.activemq.ActiveMQConnectionFactory.<init>(ActiveMQConnectionFactory.java:117) at org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(ActiveMQInitialContextFactory.java:201) at org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(ActiveMQInitialContextFactory.java:140) at org.apache.activemq.jndi.ActiveMQInitialContextFactory.getInitialContext(ActiveMQInitialContextFactory.java:65) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at ch.qos.logback.core.net.JMSAppenderBase.buildJNDIContext(JMSAppenderBase.java:49) at ch.qos.logback.classic.net.JMSQueueAppender.start(JMSQueueAppender.java:89) at ch.qos.logback.core.joran.action.AppenderAction.end(AppenderAction.java:89) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:310) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:173) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:154) at ch.qos.logback.core.joran.spi.EventPlayer.play(EventPlayer.java:48) at ch.qos.logback.core.joran.spi.Interpreter.play(Interpreter.java:336) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:96) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:74) at ch.qos.logback.core.joran.GenericConfigurator.doConfigure(GenericConfigurator.java:38) at ch.qos.logback.classic.util.ContextInitializer.configureByResource(ContextInitializer.java:23) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:34) at ch.qos.logback.classic.util.ContextInitializer.autoConfig(ContextInitializer.java:43) at org.slf4j.impl.StaticLoggerBinder.initialize(StaticLoggerBinder.java:62) at org.slf4j.impl.StaticLoggerBinder.<init>(StaticLoggerBinder.java:53) at org.slf4j.impl.StaticLoggerBinder.<clinit>(StaticLoggerBinder.java:48) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:60) at foo.bar.testbed.LoggerTester.main(LoggerTester.java:9) Caused by: java.lang.IllegalStateException: Logging factory implementation cannot be null. See also http://www.slf4j.org/codes.html#null_LF at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:86) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:155) at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:131) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:204) at org.apache.activemq.ActiveMQPrefetchPolicy.<clinit>(ActiveMQPrefetchPolicy.java:30) ... 29 more Failed to instantiate logger [ch.qos.logback.classic.selector.ContextSelector] Reported exception: java.lang.IllegalStateException: contextSelector cannot be null. See also http://logback.qos.ch/codes.html#null_CS at org.slf4j.impl.StaticLoggerBinder.getLoggerFactory(StaticLoggerBinder.java:98) at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:60) at foo.bar.testbed.LoggerTester.main(LoggerTester.java:9) Exception in thread "main" java.lang.IllegalStateException: Logging factory implementation cannot be null. See also http://www.slf4j.org/codes.html#null_LF at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:101) at foo.bar.testbed.LoggerTester.main(LoggerTester.java:9) However, removing the SLF4J commons bridge and un-excluding the commons libs from activemq results in the correct behavior. At this point the commons logging is not running through SLF4J at this point. So this is not desirable. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 1

[Bug 143] New: DynamicClassLoadingException trying to use customAppender
by bugzilla-daemon＠pixie.qos.ch 04 Apr '08

04 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=143 Summary: DynamicClassLoadingException trying to use customAppender Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: Joran AssignedTo: logback-dev(a)qos.ch ReportedBy: mark_z(a)charter.net I'm trying to use a custom Appender with Logback under a WebSphere 6.1 application, but am failing upon Logback configuration with a ch.qos.logback.core.util.DynamicClassLoadingException, caused by a java.lang.ClassNotFoundException . A search on this mailing list for "DynamicClassLoadingException" returned 0 results, and neither the documentation nor Google were of any further help. Here's my setup: EAR: - logback-classic-0.9.9.jar - logback-core-0.9.9.jar - slf4j-api-1.5.0.jar - ... WAR (configured to PARENT_LAST): - logback.xml - com.ziesemer.test.TestAppender I will attach the stack trace / STDOUT, as it is a bit lengthy (141 lines). -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 1

[Bug 137] New: add option to FileAppender to auto-create parent directories
by bugzilla-daemon＠pixie.qos.ch 03 Apr '08

03 Apr '08

http://bugzilla.qos.ch/show_bug.cgi?id=137 Summary: add option to FileAppender to auto-create parent directories Product: logback-core Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P1 Component: Appender AssignedTo: logback-dev(a)qos.ch ReportedBy: bruno.navert(a)morganstanley.com FileAppender should be able to automatically create parent directories as needed when writing the log file. For instance, if configured with <File>/var/tmp/project_name/some_file.log</File>, and the new option set to true (suggest <CreateParentDirectories>true</CreateParentDirectories> maybe), then in FileAppender.setFile(), it should do new File( fileName ).getParentFile().mkdirs() workaround is to create the directory before initializing logback. Possible but far less than ideal, and rather complicated too -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2