Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 5608 invoked from network); 7 Feb 2006 15:39:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Feb 2006 15:39:21 -0000 Received: (qmail 57405 invoked by uid 500); 7 Feb 2006 15:38:52 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 57387 invoked by uid 500); 7 Feb 2006 15:38:52 -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 57376 invoked by uid 99); 7 Feb 2006 15:38:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2006 07:38:52 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [141.15.30.12] (HELO mail02.verwalt-berlin.de) (141.15.30.12) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2006 07:38:50 -0800 Received: from localhost (localhost [127.0.0.1]) by mail02.verwalt-berlin.de (Postfix) with ESMTP id 1D58256FA7 for ; Tue, 7 Feb 2006 16:38:29 +0100 (CET) Received: from mail02.verwalt-berlin.de ([127.0.0.1]) by localhost (mail02 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22820-03 for ; Tue, 7 Feb 2006 16:38:29 +0100 (CET) Received: from quappe.verwalt-berlin.de (quappe.verwalt-berlin.de [10.0.50.189]) by mail02.verwalt-berlin.de (Postfix) with ESMTP id EDD4E56F98 for ; Tue, 7 Feb 2006 16:38:28 +0100 (CET) Received: from itdzex001.ITDZ.verwalt-berlin.de (barsch.verwalt-berlin.de [10.0.50.28]) by quappe.verwalt-berlin.de (Postfix) with ESMTP id E14A956F93 for ; Tue, 7 Feb 2006 16:38:28 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: Why JasperException "Unable to compile" Date: Tue, 7 Feb 2006 16:38:27 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Why JasperException "Unable to compile" Thread-Index: AcYr7tX7d5KQ5vBVQPu93mfhVFGHCwAAVizQAAIrgjA= From: To: X-Virus-Scanned: by interscan at verwalt-berlin.de X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > -----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" >=20 >=20 > > From: Ralph.Grothe@itdz-berlin.de=20 > > [mailto:Ralph.Grothe@itdz-berlin.de]=20 > > Subject: Why JasperException "Unable to compile" > >=20 > > we run two Tomcats on two separate hosts which are assumed=20 > > to be configured exactly the same (at least as far as Tomcat, > > Java env, and this webapp are concerned). >=20 > 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=3D ps -x -C java -o args COMMAND /opt/java1.4/bin/PA_RISC2.0/java -Xverbosegc:file=3D/tmp/gc.out -Xms1280m -Xmx1280m -Xmn786m -XX:+DisableExplicitGC -XdoCloseWithReadPending -Djava.security.policy=3D=3D/opt/hpapache2/tomcat/bin/../conf/tomcat. policy -Dtomcat.home=3D/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=3D/opt/java1.4 CATALINA_HOME=3D/opt/hpapache2/tomcat =20 # $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 =20 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 >=20 > > Maybe I could even raise the verbosity level (by somehow enabling > > debug mode) of Tomcat? Can this be done on a running Tomcat? >=20 > Try using the admin app that is available for whatever Tomcat level > you're using. >=20 > > Since I even lack the most basics of JSP (thought it was=20 > > only some sort of templating/embedding of Java code in=20 > > ordinary XHTML) >=20 > 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 >=20 Honestly, I would like to but if I were required to read all the docs=20 (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 >=20 > Upon first reference to the .jsp page. >=20 > - Chuck >=20 >=20 > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE=20 > PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete=20 > the e-mail > and its attachments from all computers. >=20 > ----------------------------------------------------------------- ---- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org >=20 >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org