Bug 38389 - java.util.Arrays.Sort() crashes with AbstractMethodError when compiled using JDT, but works OK when compiled with ant
Summary: java.util.Arrays.Sort() crashes with AbstractMethodError when compiled using ...
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Unknown (show other bugs)
Version: 5.5.14
Hardware: Other Windows 2000
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2006-01-25 21:28 UTC by Paul Hamer
Modified: 2006-06-16 04:38 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Paul Hamer 2006-01-25 21:28:03 UTC
I'm actually using Tomcat 5.5.15, but I could't select it in the list. But I've 
also got this problem with 5.5.12.

I've got the following awfully simple JSP:
<%@ page import="java.util.Arrays,java.util.Comparator" %>
  MyClass[] list = new MyClass[2];
  list[0] = new MyClass();
  list[1] = new MyClass();
  Arrays.sort(list,new Comparator<MyClass>()
              public int compare(MyClass mo1, MyClass mo2)
                return -1; // whatever
  public class MyClass
    String text = "blah";
    public String getText() { return text; }
It compiles fine, but when executed it crashes like this:

java.lang.AbstractMethodError: org.apache.jsp.error_jsp$1.compare
	at java.util.Arrays.mergeSort(Arrays.java:1284)
	at java.util.Arrays.sort(Arrays.java:1223)
	at org.apache.jsp.error_jsp._jspService(org.apache.jsp.error_jsp:64)

At first I thought it's a JDK error, but when I replace Tomcat's jasper-
compiler-jdt.jar by an Ant-compiler jar, the code runs fine !!

The above code also runs fine when I replace "MyClass" by "Object" in the 
Comparator definition, but this is ofcourse not what Java 5 is about :-)

I've already updated to Suns JDK 1.5.0_06, but that didn't change anything.

Any clues? Tanx!
Comment 1 Peter Rossbach 2006-01-25 21:36:26 UTC
Have you set the correct jspServlet compiler init parameter for jdt java 5 support?


Comment 2 Paul Hamer 2006-01-25 21:41:46 UTC
Yep, my other JSPs are filled with Java 5 specific stuff and compile/run fine. 
But, just to be sure I checked the web.xml anyway: it's indeed correctly set to 
sourceVM and targetVM 1.5
Comment 3 Peter Rossbach 2006-01-25 22:03:48 UTC
Strange, but it seams like a real JDT 3.1 bug.
Please report this to the JDT eclipse community.

Comment 4 Olivier Thomann 2006-01-26 05:31:25 UTC
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=125254 for explanation about
this problem.
Comment 5 Peter Rossbach 2006-01-26 08:00:29 UTC
Great, I have commit the patch from Olivier.

Many thanks for your help to fix it
Comment 6 Olivier Thomann 2006-01-26 16:38:07 UTC
No problem. We might consider adding some validation in the Compiler constructor
to prevent such cases.
If you would get an exception or an error immediately before the compilation,
this would never happen. We were in a case where the compilation looks good, but
because the bridge method was not generated at runtime an AbstractMethodError is
thrown. This is not good.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=125340 for this enhancement
request against JDT/Core component.
Comment 7 Evgenii Philippov 2006-06-16 11:38:21 UTC
(Just a resolution conclusion comment.)


This problem is fixed in Tomcat 5.5.16.

Tomcat 5.5.16 changelog:
( http://tomcat.apache.org/tomcat-5.5-doc/changelog.html )

"Jasper: 38389: Set correct JDT Compiler option to java 1.5 compliance. Patch
from Olivier Thomann and Paul Hamer (pero)"