Return-Path:
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 31643 invoked from network); 18 Oct 2005 21:28:31 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 18 Oct 2005 21:28:31 -0000
Received: (qmail 27710 invoked by uid 500); 18 Oct 2005 21:28:14 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 26917 invoked by uid 500); 18 Oct 2005 21:28:12 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: "Tomcat Users List"
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 26906 invoked by uid 99); 18 Oct 2005 21:28:12 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2005 14:28:12 -0700
X-ASF-Spam-Status: No, hits=0.0 required=10.0
tests=HTML_MESSAGE
X-Spam-Check-By: apache.org
Received-SPF: unknown ipv4:208.179.178.0/24 (asf.osuosl.org: encountered
unrecognized mechanism during SPF processing of domain of
David.Rickard@techbooks.com)
Received: from [208.179.178.49] (HELO gtsmail.gtsgraphics.com)
(208.179.178.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2005 14:28:11 -0700
Received: from DAVID4.techbooks.com (davidr-pc1.internal.la.gtsgraphics.com
[192.168.52.55] (may be forged))
by gtsmail.gtsgraphics.com (8.9.2/8.9.2) with ESMTP id OAA23230
for ; Tue, 18 Oct 2005 14:27:45 -0700 (PDT)
Message-Id: <6.0.1.1.0.20051018140300.01aeb710@mail.techbooks.com>
X-Sender: davidr@mail.techbooks.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 18 Oct 2005 14:25:56 -0700
To: users@tomcat.apache.org
From: David Rickard
Subject: Sending Again: Tomcat Will Not Compile JSPs
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_26550859==.ALT"
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
--=====================_26550859==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
System: Solaris SunOS 5.9
Apache: 2.0.52
Tomcat: 4.1.29
Mod JK: 1.2.6
JDK: 1.4.2_02
We have used the above Apache-Tomcat installation for 1-2 years. Within
the last few days, Tomcat has started failing to compile JSPs.
When either a new (previously unvied) or modified JSP is requested, Tomcat
throws the following error message:
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: -1 in the jsp file: null
Generated servlet error:
[javac] Compiling 1 source file
Tomcat is otherwise behaving normally: unmodified pages load and behave
normally.
There are repetitive ClassNotFoundException messages in catalina.out for
various jasper and naming classes (org.apache.jasper.runtime.HttpJspBase,
org.apache.jasper.runtime.TagHandlerPool,
org.apache.jasper.servlet.JspServlet,
org.apache.naming.java.javaURLContextFactory, ).
The Jasper jars (jasper-runtime.jar, jasper-compiler.jar) are listed in
catalina.out as "repositories," but not as "available" extensions under the
StandardClassLoader.
We have replaced the contents of common/lib from a fresh download (same
Tomcat version), without result.
Tomcat/Jasper is able to write the java file for a new/modified JSP under
work/Standalone/myserver/myapp/, but does not write the class file;
i.e., putting My_JSP.jsp:
Test Page
Generic Content: My JSP
under myapp & requesting the page generates My_JSP_jsp.java:
package org.apache.jsp;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.servlet.jsp.*;
import org.apache.jasper.runtime.*;
public class My_JSP_jsp extends HttpJspBase {
private static java.util.Vector _jspx_includes;
public java.util.List getIncludes() {
return _jspx_includes;
}
public void _jspService(HttpServletRequest request, HttpServletResponse
response)
throws java.io.IOException, ServletException {
JspFactory _jspxFactory = null;
javax.servlet.jsp.PageContext pageContext = null;
HttpSession session = null;
ServletContext application = null;
ServletConfig config = null;
JspWriter out = null;
Object page = this;
JspWriter _jspx_out = null;
try {
_jspxFactory = JspFactory.getDefaultFactory();
response.setContentType("text/html;charset=ISO-8859-1");
pageContext = _jspxFactory.getPageContext(this, request, response,
null, true, 8192, true);
application = pageContext.getServletContext();
config = pageContext.getServletConfig();
session = pageContext.getSession();
out = pageContext.getOut();
_jspx_out = out;
out.write("\n");
out.write("");
out.write("Test Page");
out.write("");
out.write("\n");
out.write("");
out.write("");
out.write("
Generic Content: My JSP");
out.write("
");
out.write("");
out.write("\n");
out.write("\n");
} catch (Throwable t) {
out = _jspx_out;
if (out != null && out.getBufferSize() != 0)
out.clearBuffer();
if (pageContext != null) pageContext.handlePageException(t);
} finally {
if (_jspxFactory != null) _jspxFactory.releasePageContext(pageContext);
}
}
}
but not My_JSP_jsp.class. Tomcat's ability to write the java file under
/work would seem to rule out permissions issues with that directory.
Also, we can compile and run stand-alone Java classes using the 1.4.2_02 JDK.
The net condition is: Tomcat is running, and can serve compiled JSPs and
servlets without errors; Tomcat cannot compile new/modified JSPs; and
Tomcat/Jasper seem to be losing file names between generating *_jsp.java
and *_jsp.class (note the "jsp file: null" in the error message).
Any ideas?
--
David Rickard
Software Engineer
TechBooks/GTS
Your Single Source Solution!
Los Angeles CA * York, PA * Boston,MA * New Delhi, India
Visit us on the World Wide Web
http://www.techbooks.com
david.rickard@techbooks.com
5650 Jillson St., Los Angeles, CA 90040
(323) 888-8889 x331
(323) 888-1849 (Fax)
--=====================_26550859==.ALT--