Tomcat administration: Difference between revisions
No edit summary |
|||
| Line 6: | Line 6: | ||
This means everything sending stuff to the standard output (for example a console appender in Log4J) won't work. '''This also means that stack trace logs (caused by exceptions) are not going to be available, since they are outputted to stdout.''' | This means everything sending stuff to the standard output (for example a console appender in Log4J) won't work. '''This also means that stack trace logs (caused by exceptions) are not going to be available, since they are outputted to stdout.''' | ||
== Tomcat Logging == | |||
If Tomcat finds the log4j.jar on its classpath, it will use log4j as its logging system. And if log4j is not configured at all, *nothing* will be printed anywhere. So if you want to disable log4j logging and use JDK logging, you must delete the log4j.jar, it is not sufficient to delete or remove the log4j.properties file. | |||
Revision as of 16:30, 19 March 2007
Tomcat is a servlet container, and as such can be used to deploy web applications using Java on the server side.
Tomcat on Gentoo
Currently (19/03/2007), the init scripts on Gentoo are not able to redirect Tomcat's standard output to a file. This is bug 162379 in Gentoo's bugzilla.
This means everything sending stuff to the standard output (for example a console appender in Log4J) won't work. This also means that stack trace logs (caused by exceptions) are not going to be available, since they are outputted to stdout.
Tomcat Logging
If Tomcat finds the log4j.jar on its classpath, it will use log4j as its logging system. And if log4j is not configured at all, *nothing* will be printed anywhere. So if you want to disable log4j logging and use JDK logging, you must delete the log4j.jar, it is not sufficient to delete or remove the log4j.properties file.