Re: [S2] Logging Issues

Hi Laurie, Thanks for the reply! I found the "swallowOutput" attribute in the Tomcat context that caused the exceptions to be placed in my application log. However, I'm now setting up global exception mapping in struts so I can handle unexpected problems without showing the user a stack trace

Re: [S2] Logging Issues

You can't have log4j route exception errors to the log file if you don't catch the exception and pass it to log4j... If you allow the exception to propagate all the way up, it will be logged by the container. Short story: if you want to control where something gets logged to, you need to contro

[S2] Logging Issues

r.org.apache.struts2=WARN log4j.logger.org.springframework=WARN log4j.logger.org.hibernate=WARN log4j.logger.org.apache.jasper=WARN log4j.logger.org.apache.catalina=WARN log4j.logger.com.opensymphony.xwork2=WARN -- View this message in context: http://www.nabble.com/-S2--Logging-Issues-tp16399078p16399078.html Sent from