tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Why JasperException "Unable to compile"
Date Tue, 07 Feb 2006 13:56:26 GMT
Hi Tomcatters,

we run two Tomcats on two separate hosts which are assumed to be
configured exactly the same
(at least as far as Tomcat, Java env, and this webapp are

I have no knwoledge of Tomcat webapps like JSPs and Jasper
(only administrating the server).

While when the same query path of the URI is called from a
client's browser against both hosts,
and the same piece of JSP should get executed there, it works
fine on one host
whereas on the other Tomcat host we get a Jasper exception.

Because of my lack of knowledge of Jasper I cannot find the
source of the error
where both Tomcat hosts could possibly deviate from one another.
If it was a legacy CGI program or script I would know how to help

Here is the exception pass stack trace through the Jasper classes
from the host where this particular request crashes,
taken from its Tomcat log.

Maybe any Java/Jasper knwoledgeable person can detect something
from it?

Maybe I could even raise the verbosity level (by somehow enabling
debug mode) of Tomcat?
Can this be done on a running Tomcat?
How could I raise the logging level to Debug,
maybe by passing the Java master thread some -D switch
But this would then require a Tomcat restart I suppose?

Since I even lack the most basics of JSP
(thought it was only some sort of templating/embedding of Java
code in ordinary XHTML)
I am not even familiar with when and how the Java source gets
compiled and thus could produce
the below Jasper exception (it simply suggests a wrong invocation
of the Java compiler, as it looks)
Wasn't it that servlets or JSP got only compiled the first time
they were executed by the servlet engine,
and thereafter remain resident in memory?

Excerpt from Tomcat log, where the Jasper exception is thrown:

  1343  2006-02-07 13:59:46 - Ctx(/OurTool) : Exception in R(
/OurTool + /someTrash/rotten.jsp + null) -
org.apache.jasper.JasperException: Unable to compile Usage:
jsp->javac <options> <source files>
  1345  where <options> includes:
  1346    -g                     Generate all debugging info
  1347    -g:none                Generate no debugging info
  1348    -g:{lines,vars,source} Generate only some debugging
  1349    -O                     Optimize; may hinder debugging
or enlarge class files
  1350    -nowarn                Generate no warnings
  1351    -verbose               Output messages about what the
compiler is doing
  1352    -deprecation           Output source locations where
deprecated APIs are used
  1353    -classpath <path>      Specify where to find user class
  1354    -sourcepath <path>     Specify where to find input
source files
  1355    -bootclasspath <path>  Override location of bootstrap
class files
  1356    -extdirs <dirs>        Override location of installed
  1357    -d <directory>         Specify where to place generated
class files
  1358    -encoding <encoding>   Specify character encoding used
by source files
  1359    -target <release>      Generate class files for
specific VM version
  1361          at
  1362          at
  1363          at
  1364          at
  1365          at
  1366          at
  1367          at
  1368          at
  1369          at
  1370          at


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message