Got back to working on Tomcat again after several day's haitus. The last problem is gone but now Tomcat is encountering a new one: On startup, Tomcat seems to successfully go through the first part of its starup routine - it deploys the JAR files in its own WEB-INF/library directory to my site's library directory, then it starts following the script in the web.xml file in its own directory, and successfully loads something called container servlet default and container servlet invoker. Then it gets hung up trying to load the JSP servlet. I get the following error message in the error log:
StandardWrapper[:jsp]: Marking servlet jsp as unavailable StandardContext: Servlet threw load() exception: javax.servlet.ServletException: Error instantiating servlet class org.apache.jasper.servlet.JspServlet javax.servlet.ServletException: Error instantiating servlet class org.apache.jasper.servlet.JspServlet
The script in the web.xml file related to this is:
"The JSP page compiler and execution servlet, which is the mechanism used by Tomcat to support JSP pages. Traditionally, this servlet is mapped to URL patterh "*.jsp". This servlet supports the following initialization parameters (default values are in square brackets:" Then it goes on to give a bunch of initialization parameters.
I have not been able to find any answers to the same problem using Google, etc. There was one post on this site at http://www.coderanch.com/t/81863/Tomcat/WEB-INF-breaking-Context-root where someone prevented a similar load error by removing another file called servlet.jar (or preventing it from being deployed) in his web.xml file. But that error wasn't occuring on startup.
For what it's worth I'm running Tomcat 4 on Linux.
Joined: Mar 30, 2005
Something I forgot to mention. I searched for anything called "jsp.class" or "jsp.java" using the find command, but found nothing. I did find several files called "jsp.*" or "*jsp.*" with different beginnings and endings, such as several "jsp.vim" files and a few "jsptoservlet.jsp" files. Still, doesn't the error message imply that the offending servlet is there, but something has gone wrong in loading it???