/var/jakarta-tomcat-5.5.4/logs/tomcat.log.You can (and should) be more picky about which packages to include - in the logging. For example try substituting the - last line of the above configuration with one of these: - + in the logging. Tomcat 5.5 uses a new way of restricting logs by Engine + name and Host. For example, for a default Catalina localhost log, add this to the + end of the log4j.properties above. Note that there are known issues with + using this naming convention (with square brackets) in log4j XML based + configuration files, so we recommend you use a properties file as described + until a future version of log4j allows this convention.
- Your web applications should certainly use their own log4j configuration. - This is valid with the above. You would place a similar log4j.properties + In addition, your web applications should use their own log4j configuration. + This is valid with the above configuration. You would place a similar log4j.properties file in your web application's WEB-INF/classes folder, and log4j1.2.8.jar into - WEB-INF/lib. Then specify your package level logging. This is a basic setup of log4j + WEB-INF/lib (commons-logging is not required in this instance). + Then specify your package level logging. This is a basic setup of log4j and you should consult the log4j documentation - for more options: this page is intended only as a bootstrapping guide. + for more options. Note: this page is intended only as a bootstrapping guide.