[ https://issues.apache.org/jira/browse/SLING-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-527. ----------------------------------- Resolution: Fixed Fix Version/s: 2.0.1 In Rev. 667106 fixed inclusion of the commons/testing library in the war file. This solves the issue and this can be closed. > NullPointerException running the launchpad/webapp > ------------------------------------------------- > > Key: SLING-527 > URL: https://issues.apache.org/jira/browse/SLING-527 > Project: Sling > Issue Type: Bug > Components: Commons Log, Launchpad Launcher > Reporter: Felix Meschberger > Assignee: Felix Meschberger > Fix For: 2.0.1 > > > After the latest changes to commons/log, there are NullPointerExceptions when > running the launchpad/webapp with Maven -- both with integration-tests and > jetty:run. > The stacktraces at startup are as follows: > [INFO] Context path = / > [INFO] Tmp directory = /usr/src/sling/head/launchpad/webapp/target/work > [INFO] Web defaults = jetty default > [INFO] Web overrides = none > [INFO] Webapp directory = > /usr/src/sling/head/launchpad/webapp/target/org.apache.sling.launchpad.webapp-3-incubator-SNAPSHOT > [INFO] Starting jetty 6.1.5 ... > 2008-06-12 15:15:26.283::INFO: jetty-6.1.5 > 2008-06-12 15:15:26.403::INFO: No Transaction manager found - if your webapp > requires one, please configure one. > 2008-06-12 15:15:31.140:/:WARN: ERROR: EventDispatcher: Error during > dispatch. (java.lang.NullPointerException) > java.lang.NullPointerException > at > org.apache.sling.commons.log.slf4j.LogConfigManager.getLoggerConfig(LogConfigManager.java:551) > at > org.apache.sling.commons.log.slf4j.LogConfigManager.getLogger(LogConfigManager.java:179) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:88) > at > org.apache.sling.commons.log.LogSupport.getLogger(LogSupport.java:322) > at org.apache.sling.commons.log.LogSupport.logOut(LogSupport.java:333) > at > org.apache.sling.commons.log.LogSupport.fireLogEvent(LogSupport.java:167) > at > org.apache.sling.commons.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:619) > 2008-06-12 15:15:31.141:/:WARN: ERROR: EventDispatcher: Error during > dispatch. (java.lang.NullPointerException) > java.lang.NullPointerException > at > org.apache.sling.commons.log.slf4j.LogConfigManager.getLoggerConfig(LogConfigManager.java:551) > at > org.apache.sling.commons.log.slf4j.LogConfigManager.getLogger(LogConfigManager.java:179) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:88) > at > org.apache.sling.commons.log.LogSupport.getLogger(LogSupport.java:322) > at org.apache.sling.commons.log.LogSupport.logOut(LogSupport.java:333) > at > org.apache.sling.commons.log.LogSupport.fireLogEvent(LogSupport.java:167) > at > org.apache.sling.commons.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:619) > 2008-06-12 15:15:31.331:/:INFO: sling: Servlet sling initialized > 2008-06-12 15:15:31.343::INFO: Started [EMAIL PROTECTED]:8888 > [INFO] Started Jetty Server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.