tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34110] The message "SEVERE: Error listenerStart" should be more explicit
Date Fri, 03 Apr 2009 18:45:45 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110





--- Comment #4 from Dan Armbrust <daniel.armbrust.list@gmail.com>  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


Mime
View raw message