Community
Participate
Working Groups
Version: 3.0.1 Build id: 200408050912 An AbstractMethodError thrown by a JDT type prevents our tool from running. This problem occurred 2 out of 3 times that our tool was run. I'm marking this defect "critical" instead of "blocker" because the run did complete once without the error being thrown. There are several different stack traces (different because they start at a different method), but all end at the same place. Here's the top of one stack trace: java.lang.AbstractMethodError: org/eclipse/jdt/core/IJavaElement.getElementType ()I at org.eclipse.jdt.internal.core.JavaModelCache.peekAtInfo (JavaModelCache.java:88) at org.eclipse.jdt.internal.core.JavaModelManager.removeInfoAndChildren (JavaModelManager.java:1575) at org.eclipse.jdt.internal.core.JavaElement.close(JavaElement.java:90) at org.eclipse.jdt.internal.core.CompilationUnit.close (CompilationUnit.java:181) at org.eclipse.jdt.internal.core.ElementCache.close (ElementCache.java:51) at org.eclipse.jdt.internal.core.OverflowingLRUCache.privateRemoveEntry (OverflowingLRUCache.java:295) at org.eclipse.jdt.internal.core.OverflowingLRUCache.makeSpace (OverflowingLRUCache.java:183) at org.eclipse.jdt.internal.core.OverflowingLRUCache.put (OverflowingLRUCache.java:362) at org.eclipse.jdt.internal.core.JavaModelCache.putInfo (JavaModelCache.java:121) at org.eclipse.jdt.internal.core.JavaModelManager.putInfos (JavaModelManager.java:1480) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed (JavaElement.java:586) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo (JavaElement.java:309) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo (JavaElement.java:295) at org.eclipse.jdt.internal.core.SearchableEnvironment.find (SearchableEnvironment.java:87) at org.eclipse.jdt.internal.core.SearchableEnvironment.findType (SearchableEnvironment.java:147) at org.eclipse.jdt.core.dom.CompilationUnitResolver$CancelableNameEnvironment.findT ype(CompilationUnitResolver.java:75) at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType (LookupEnvironment.java:75) at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve (UnresolvedReferenceBinding.java:30) at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superInterfaces (BinaryTypeBinding.java:476) at org.eclipse.jdt.core.dom.TypeBinding.getInterfaces (TypeBinding.java:219)
Could you please let us know what VM you are using? This might be a class loading issue that has nothing to do with JDT/Core. *** This bug has been marked as a duplicate of 65098 ***
java -version java version "1.4.2" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142-20040810 (JIT ena bled: jitc))
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
This enhancement/defect was mistaken closed as part of the TPTP 4.6 Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes) since the originator of this enhancement/defect has an inactive Bugzilla account. If this enhancement/defect is still unresolved and reproducible, please re-open.
