https://issues.apache.org/bugzilla/show_bug.cgi?id=34110
--- Comment #3 from Dan Armbrust <daniel.armbrust.l...@gmail.com> 2009-04-02 13:48:36 PST --- I ran into this issue where tomcat was not giving me any information to go on with one of my webapps. After a long search, documented here: http://marc.info/?t=123861720500002&r=1&w=2 we discovered that the sequence of events which leads tomcat to not log any debug information about the error is as follows: You deploy a war file to tomcat which includes log4j.jar, and has a listener declared in the web.xml file. The listener in the web.xml file points to a class that doesn't exist. This will cause the deployment to fail. The war file that you deploy does _NOT_ include a log4j.properties or log4j.xml file in the WEB-INF/classes folder - presumably because your webapp dynamically configures log4j in a different manner. The end result is, there is some period of time during deployment of the webapp when tomcat attempts to log deployment messages to log4j which was supplied by your webapp - but since the log4j within the webapp is not yet configured, the messages are lost. I'm not sure if there is anything that can be done to improve this situation. An obvious solution for me is to supply a log4j.properties file which will be used to configure log4j for the short period of time before my dynamic configuration runs. But it seems like Tomcat should always log issues during deployment into its own logging system, rather than trying to send them into the webapps logging system. Here is a vote to re-open this bug. -- 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-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org