Startup failed due to previous errors

This newly established project, released to Tomcat above the time, always prompt startup failed due to previous errors;

The complete error message is:

Info: Container org.apache.catalina.core.ContainerBase. [Catalina]. [localhost]. [/bpslocal] have not been started
2010-10-19 22:56:53 Org.apache.catalina.loader.WebappClassLoader Validatejarfile
Info: Validatejarfile (C:/primeton/bps/apache-tomcat-5.5.20/webapps/bpslocal/web-inf/lib/j2ee.jar)-jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending Class:javax/servlet/servlet.class
Log4j:warn No Appenders could is found for logger (org.apache.commons.digester.Digester.sax).
Log4j:warn Initialize the log4j system properly.
2010-10-19 22:56:53 org.apache.catalina.core.StandardContext Start
Severity: Error Listenerstart
2010-10-19 22:56:53 org.apache.catalina.core.StandardContext Start
Severity: Context [/bpslocal] startup failed due to previous errors

First search keyword error, the result gives the opinion is my bag superfluous, deleted me an afternoon, also did not fix, the mood is very irritable. When I see this passage, I find out the problem. I used the tool to add some XML configuration information to my deployment before it was deployed, causing some servlets to not exist and then not starting up.

Author: Hongyiqiye Link: http://hongyiqiye.javaeye.com/blog/266068

The startup failed due to previous errors error is often sent when deploying apps on Tomcat. This error often makes people not feel the brain. Here are a few things to find out:

1.web.xml file, this file defines a lot of web services that are required to start the class, XML files, and if these cannot be found, a startup failed due to previous errors error occurs.

2. If you use spring, the class that is defined in Applicationcontext.xml, the XML file, is not found and the error is reported.

3. If you use Ibatis, the XML file defined in Sqlmapconfig.xml will also be reported in this error.

The experience is to make sure that each piece of information defined in the configuration file is clear and not used by someone else's code, which will solve the problem.