Tomcat: The Definitive Guide, 2nd Edition

Hunting for Errors

For the sake of example, suppose that you notice that one web application was inaccessible from a browser. In the access logfile, Tomcat indicated a 404 error, which you took to mean that a file was missing.

However, it's easy to verify that all required files are present, as they are in this example. The next step in hunting for errors is to examine the catalina.out logfile, which is useful for more advanced troubleshooting. Example 8-1 shows a small excerpt from the catalina.out file after running Tomcat with several web applications.

Example 8-1. catalina.out logfile excerpt

XmlMapper: org.apache.catalina.core.StandardContext.addMimeMapping( Z, application/x-c ompress) XmlMapper: org.apache.catalina.core.StandardContext.addMimeMapping( z, application/x-c ompress) XmlMapper: org.apache.catalina.core.StandardContext.addMimeMapping( zip, application/z ip) XmlMapper: org.apache.catalina.core.StandardContext.addWelcomeFile( index.html) XmlMapper: org.apache.catalina.core.StandardContext.addWelcomeFile( index.htm) XmlMapper: org.apache.catalina.core.StandardContext.addWelcomeFile( index.jsp) XmlMapper: Set locator : org.apache.crimson.parser.Parser2$DocLocator@bec295b8 Resolve: -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com//d tds/web-app_2_3.dtd Using alternate DTD /javax/servlet/resources/web-app_2_3.dtd XmlMapper: org.apache.catalina.core.StandardContext.setPublicId(-//Sun Microsystems, I nc.//DTD Web Application 2.3//EN) XmlMapper: org.apache.catalina.core.StandardContext.setDisplayName(Ian ...