Interesting response... The exact same JSP is compiling on two other machines. Your right though, manually compiling it is a good next step (one that I'm ashamed to say I didn't think of myself), so I'm off to do that now. Maybe I have a corrupt file in some minor, hard-to-detect way that is causing a problem on this one Tomcat instance. Thanks for the suggestion, it's a logical course of action.

--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

Ryan Stewart wrote:
Quite simply, you have an error in your JSP that is preventing the translated 
servlet from compiling. If you don't know where to look for the compiler 
output, then just go and manually compile the servlet.

-----Original Message-----
From: "Frank W. Zammetti"<[EMAIL PROTECTED]>
To: "Tomcat User"<tomcat-user@jakarta.apache.org>
Date: Thu Dec 30 06:53:31 PST 2004
Subject: JSP compilation problem

[...]

HTTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP

[...]

root cause
Compile failed; see the compiler error output for details.

[...]

___________________________________________________
Check-out GO.com
GO get your free GO E-Mail account with expanded storage of 6 MB!
http://mail.go.com



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to