On Thu, Apr 2, 2009 at 7:30 PM, Dan Armbrust <daniel.armbrust.l...@gmail.com> wrote: > > What would be doing this? Something in my app is preventing this > severe error from being passed up to tomcat to be logged - but then my > app doesn't log it either - probably because it is stopped before it > ever finishes deploying.
Your app can't logg /before/ being deployed - that's Tomcat's responsibility. > There is obviously some interaction going on > between my webapp and tomcat's logging system that I don't know about. - Check out if you find a file like log4j.properties or log4j.xml within your Tomcat-subdirectories (not within you webapps!) and rename it - Check for a file named log4j*.jar and rename it - Check for a file logging.properties within your Tomcat-subdirectories (not within you webapps!) and rename it - Replace the renamed file "logging.properties" with one from a clean Tomcat-installation - Restart Tomcat Now if there's an error with the deployment, you should find that within Tomcat's logs. Rgds Gregor -- just because your paranoid, doesn't mean they're not after you... gpgp-fp: 79A84FA526807026795E4209D3B3FE028B3170B2 gpgp-key available @ http://pgpkeys.pca.dfn.de:11371 @ http://pgp.mit.edu:11371/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
