tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kupper ext-FA, Thomas" <thomas.kupper....@siemens.com>
Subject Jasper Compiling Error -> return type incompatible with JspSourceDependent.getDependants
Date Thu, 27 Jan 2011 08:09:02 GMT
Hello,

We got two Redhat 5.6 Server which are set up idential in the area of tomcat and java. But
we have the problem that on the productive machine compilation of JSP files fails with the
error 'return type incompatible with JspSourceDependent.getDependants'. The exact same application
compiles just fine on the test machine.

It fails to compile a simple index.jsp on the productive server because the generated  index_jsp.java
files differs.

Version information:

Server version: Apache Tomcat/5.5.23
Server built:   Dec 9 2010 03:51:37
Server number:  5.5.23.0
OS Name:        Linux
OS Version:     2.6.18-238.el5
Architecture:   amd64
JVM Version:    1.6.0_22-b04
JVM Vendor:     Sun Microsystems Inc.

--- index.jsp (on both server) ---
<%
response.sendRedirect("login.jsp");
%>
-----------------

the automatically generated index_jsp.java diffiers in the following lines:

------------------------------------------------------------------------------
--- index_jsp.java_not-compiling 2011-01-27 08:38:46.000000000 +0100
+++ index_jsp.java_compiling-fine	2011-01-27 08:38:41.000000000 +0100
@@ -7,9 +7,9 @@
 public final class index_jsp extends org.apache.jasper.runtime.HttpJspBase
     implements org.apache.jasper.runtime.JspSourceDependent {
 
-  private static java.util.Vector _jspx_dependants;
+  private static java.util.List _jspx_dependants;
 
-  public java.util.List getDependants() {
+  public Object getDependants() {
     return _jspx_dependants;
   }
------------------------------------------------------------------------------

Java-wise it's clear why it won't compile. What we don't understand is why the automatically
generated *.java file differs.

We made sure both server are idential:
- both RHEL5 installation are at the exact same update level
- the same tomcat, java & jasper version (stock RHEL5.6 packages) are installed
- identical tomcat configuration files (verified by creating md5 sums of 'em in /etc/tomcat5)
- identical environment settings for the tomcat user on both servers
- tomcat is called idential (check /proc/<tomcat pid>/{cmdline,environ})
- the same user and file permission
- the web app is identical (copied from one system to the other)
- all the *.jar files are idential (verified by creating md5 sums of 'em)

Does anyone have an idea what else we could check? 
Is it possible to 'simulate' a jasper build, e.g. with a custom build.xml, manually to be
able to see what causes the error?

I asked the oracle of Google for help for almost a day but couldn't find matching solution.
One possible cause could be different versions of jasper installed. But I couldn't find anything
suspicious.

Thanks and have a good day,

Thomas Kupper
Siemens Schweiz AG
Siemens IT Solutions and Services
SIS GO SD AO
Freilagerstrasse 28, CH-8047 Zürich
Wichtiger Hinweis: Diese E-Mail und allfällige Anlagen können firmenvertrauliche Informationen
enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, benachrichtigen Sie uns bitte
durch Antwort-Mail und löschen Sie diese E-Mail nebst Anlagen von Ihrem System. Vielen Dank.


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


Mime
View raw message