tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <Ralph.Gro...@itdz-berlin.de>
Subject RE: Why JasperException "Unable to compile"
Date Tue, 07 Feb 2006 15:38:27 GMT
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
> Sent: Tuesday, February 07, 2006 3:34 PM
> To: Tomcat Users List
> Subject: RE: Why JasperException "Unable to compile"
> 
> 
> > From: Ralph.Grothe@itdz-berlin.de 
> > [mailto:Ralph.Grothe@itdz-berlin.de] 
> > Subject: Why JasperException "Unable to compile"
> > 
> > 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 concerned).
> 
> And what would that configuration be?  It's tough to answer a
question
> without knowing what Tomcat level, what JRE/JDK, what OS, etc.
You're
> asking people to guess.

Sorry, Chuck I simply forgot to post the most vital information
with my query.

Both hosts run Tomcat with the HP-UX port of Java 1.4
as can be seen from the proc table's entry for the Tomcat server
process

# UNIX95= ps -x -C java -o args
COMMAND
/opt/java1.4/bin/PA_RISC2.0/java -Xverbosegc:file=/tmp/gc.out
-Xms1280m -Xmx1280m -Xmn786m -XX:+DisableExplicitGC
-XdoCloseWithReadPending
-Djava.security.policy==/opt/hpapache2/tomcat/bin/../conf/tomcat.
policy -Dtomcat.home=/opt/hpapache2/tomcat/bin/..
org.apache.tomcat.startup.Main start


The Tomcat release to guess is a bit harder,
because the HP-UX depot that bundled Apache httpd and Tomcat
didn't come with the handy version.sh wrapper.
See it doesn't understand "version" in this incarnation


# export JAVA_HOME=/opt/java1.4
CATALINA_HOME=/opt/hpapache2/tomcat                

# $CATALINA_HOME/bin/catalina.sh version
Using CATALINA_BASE:   /opt/hpapache2/tomcat
Using CATALINA_HOME:   /opt/hpapache2/tomcat
Using CATALINA_TMPDIR: /opt/hpapache2/tomcat/temp
Using JAVA_HOME:       /opt/java1.4
Usage: catalina.sh ( commands ... )
commands:
  debug             Start Catalina in a debugger
  debug -security   Debug Catalina with a security manager
  embedded          Start Catalina in embedded mode
  jpda start        Start Catalina under JPDA debugger
  run               Start Catalina in the current window
  run -security     Start in the current window with security
manager
  start             Start Catalina in a separate window
  start -security   Start in a separate window with security
manager
  stop              Stop Catalina


There seems to be only a version.txt for Ant in the Tomcat libs,
but maybe you can guess by looking at these lines?


# find $PWD -name \*.jar|xargs -n1 $JAVA_HOME/bin/jar -tf |egrep
-i version\|release        
org/apache/xerces/impl/XMLVersionDetector.class
org/apache/xerces/impl/Version.class
org/apache/xmlcommons/Version.class
org/apache/tools/ant/version.txt
org/apache/jasper/runtime/JspFactoryImpl$PrivilegedReleasePageCon
text.class
com/sun/naming/internal/VersionHelper.class
com/sun/naming/internal/VersionHelper11.class
com/sun/naming/internal/VersionHelper11$RClassLoader.class
com/sun/naming/internal/VersionHelper11$1.class
com/sun/naming/internal/VersionHelper12.class
com/sun/naming/internal/VersionHelper12$1.class
com/sun/naming/internal/VersionHelper12$2.class
com/sun/naming/internal/VersionHelper12$3.class
com/sun/naming/internal/VersionHelper12$4.class
com/sun/naming/internal/VersionHelper12$5.class
com/sun/naming/internal/VersionHelper12$6.class
com/sun/naming/internal/VersionHelper12$InputStreamEnumeration.cl
ass
com/sun/naming/internal/VersionHelper12$7.class
org/apache/commons/beanutils/ConversionException.class
com/hp/mx/utilities/version/
com/hp/mx/utilities/version/MxVersion.class
org/apache/xalan/extensions/MethodResolver$ConversionInfo.class
org/apache/xalan/processor/XSLProcessorVersion.class


> 
> > Maybe I could even raise the verbosity level (by somehow
enabling
> > debug mode) of Tomcat? Can this be done on a running Tomcat?
> 
> Try using the admin app that is available for whatever Tomcat
level
> you're using.
> 
> > Since I even lack the most basics of JSP (thought it was 
> > only some sort of templating/embedding of Java code in 
> > ordinary XHTML)
> 
> Sounds like you should at least read the Servlet and JSP specs,
which
> are available on the Sun download site:
> http://java.sun.com/products/servlet/download.html#specs
> http://java.sun.com/products/jsp/download/index.html#specs
> 

Honestly, I would like to
but if I were required to read all the docs 
(let alone specifications and RFCs which mainly address software
implementors)
of all the services that run on the many servers I have to
administer
there wouldn't be much time left for anything else
(and this doesn't yet include comprehending their contents)


> > I am not even familiar with when and how the Java source gets
> > compiled and thus could produce the below Jasper exception
> 
> Upon first reference to the .jsp page.
> 
>  - Chuck
> 
> 
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE 
> PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If
you
> received this in error, please contact the sender and delete 
> the e-mail
> and its attachments from all computers.
> 
>
-----------------------------------------------------------------
----
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message