I just redeployed a WAR file on a Windows based Tomcat 5.5. server, after which reloading the login jsp-page resulted in the following stack trace: java.lang.NullPointerException ch.qos.logback.classic.spi.LoggingEvent.<init>(LoggingEvent.java:121) ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:437) ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:393) ch.qos.logback.classic.Logger.log(Logger.java:812) org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:120) org.apache.catalina.connector.Request.getRequestDispatcher(Request.java:1219) org.apache.catalina.connector.RequestFacade.getRequestDispatcher(RequestFacade.java:569) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:402) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144) com.foo.axsWHSweb.servlet.filters.LoggedInToAxsFreightFilter.doFilter(LoggedInToAxsFreightFilter.java:59) There is jcl-over-slf4j-1.5.5.jar, slf4j-api1.5.6, logback-classic 0.9.14 and logback-core-0.9.14 in the classpath. Is this a known and fixed issue (so I should upgrade all to the newest) or should I investigate? I believe there has been added an appender in logback.xml with a layout based on a class not present in the previous version of the war. -- Thorbjørn Ravn Andersen "...plus... Tubular Bells!"