If the database server times out a connection, the connection pool on Tomcat side would not be aware of its disconnection, and could throw the following exception in Tomcat:
How to configure your web application's stderr and stdout messages be redirected to the application's log file for Tomcat 5.5 in ERS 3.x
For standard web applications, error messages and output are streamed to log files using sterr and stdout respectively. Some application developers prefer to aggregate all these messages into the application log.
The following steps are required to configure your web application's stderr and stdout messages be redirected to the application's log file for Tomcat 5.5 in ERS 3.1 utilizing java.util.logging:
The cause for an HTTP 404 error in Tomcat.
Tomcat fails to start and return a 404 error. Java stack trace shows:
Changing log verbosity in Tomcat 4.1, 5.0 and 5.5
In Tomcat 4.1, the logVerbosityLevel attribute for the Logger element can be used to set the log level. FATAL, ERROR, WARNING, INFORMATION, and DEBUG are the valid values. The default setting is at the WARNING level.
In Tomcat 5.0, it can be changed through commons logging or log4j. Log4j is recommended as it has greater flexibility. In doing so: