0

I have the following problem: Our webapp is running on tomcat 7 and I have an exception that I would like to filter from being written in the log files. The logger is defined in the logging.properties file,

handlers = org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

followed by the directory, prefix and format.

Is there any possibility to stop tomcat from writing the exception in the file and onto the console? Because thats what happens right now. I know there are log filters for log4j, but I don't know anything for juli. The exception beeing thrown is:

org.apache.catalina.core.StandardWrapperValve invoke 
SEVERE: Servlet.service() for servlet [default] in context with path [] threw exception [javax.servlet.ServletException:

I would be glad if anyone could point me in the direction how to get this exception out of the logs.

Ideas I had so far:

  • write a doFilter servlet, that filters the exception out before it arrives at the logger
  • modifiy the the java.util.logging library files to reject this certain exception
  • route all tomcat logs through log4j and filter there
rincewind
  • 623
  • 6
  • 13

1 Answers1

2

JULI supports custom filters by extending java.util.logging.Filter.

  1. Write a custom filter to block the exception. Unit test it so you know it works.
  2. Place the filter code in the Tomcat classpath.
  3. Modify the logging.properties to install custom filter on the FileHandler and ConsoleHandler.
Community
  • 1
  • 1
jmehrens
  • 10,580
  • 1
  • 38
  • 47
  • Thank you very much, this helps a lot. Maybe also this example for a filter is nice. http://tutorials.jenkov.com/java-logging/filters.html I am going to try your anwer and report back. – rincewind Nov 19 '15 at 05:55
  • Perfect, this solved all my problems, thank you! Also this document is relevant for the classpath https://tomcat.apache.org/tomcat-7.0-doc/class-loader-howto.html – rincewind Nov 19 '15 at 12:56