Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 48569 invoked from network); 3 Apr 2009 18:53:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 18:53:17 -0000 Received: (qmail 87104 invoked by uid 500); 3 Apr 2009 18:52:31 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 86868 invoked by uid 500); 3 Apr 2009 18:52:30 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 86245 invoked by uid 99); 3 Apr 2009 18:46:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 18:46:06 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 18:46:05 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 507DA234C056; Fri, 3 Apr 2009 11:45:45 -0700 (PDT) From: bugzilla@apache.org To: dev@tomcat.apache.org Subject: DO NOT REPLY [Bug 34110] The message "SEVERE: Error listenerStart" should be more explicit X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: newchanged X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Tomcat 5 X-Bugzilla-Component: Catalina X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: daniel.armbrust.list@gmail.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: dev@tomcat.apache.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Message-Id: <20090403184545.507DA234C056@brutus.apache.org> Date: Fri, 3 Apr 2009 11:45:45 -0700 (PDT) X-Virus-Checked: Checked by ClamAV on apache.org https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 --- Comment #4 from Dan Armbrust 2009-04-03 11:45:41 PST --- Created an attachment (id=23439) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23439) webapp which reproduces the error My comment #3 was missing a step that is required to reproduce this problem. You need to have log4j and commons-logging.jar in your war file to reproduce the issue. This war file will fail to deploy due to an invalid listener in tomcat 5.5.27, and fails to log the stack trace containing the cause of the problem anywhere. The only output given is: SEVERE: Error listenerStart SEVERE: Context [/a] startup failed due to previous errors After tomcat has expanded the warfile, if you rename webapps/a/WEB-INF/classes/log4j.properties.hidden to log4j.properties - then you will get a stack trace - but only because it has been sent to the logger within the webapp. It doesn't get sent to tomcats logging system. I don't understand why tomcat is changing how it logs, depending on if log4j and commons-logging are present in the classpath of a webapp being deployed. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org