Whenever tomat compiles a JSP page and there is an error in it (for instance trying to reference a property on a bean that doesn't exist), it is throwing (and obscuring) an exception and logging it to catalina.out and then returning whatever html it has built to the browser, as in :
Sep 2, 2009 2:07:28 PM org.apache.catalina.core.ApplicationDispatcher invokeSEVERE: Servlet.service() for servlet jsp threw exception javax.el.PropertyNotFoundException: Property 'blah' not found on com.foo.bar (and then a ginormous stack trace) This would be good if I knew which host actually had this error. I have one tomcat instance server with a number of hosts, each a sandbox for a developer. Is there any way to configure the logging per host such that these errors that get logged to catalina.out get logged to a host specific log file instead of catalina.out (or as well as)? I am looking at the document at http://tomcat.apache.org/tomcat-6.0-doc/logging.html, but I just don't see/understand what I need to do. This is not to be confused with logging generated from within my context - I have that configured via logback going to its own log file successfully - it's the tomcat engine errors that I need to deal with. Or, if this isn't possible, is there a way to configure tomcat to generate that stack trace about the PropertyNotFoundException as the output html when it tries to compile the JSP instead of obscuring it and returning a partially complete html page? Thanks Chris Tomcat 6.0.20 CentOS 4 Java(TM) SE Runtime Environment (build 1.6.0_16-b01) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
