Bug 313904 - [search] An internal error occurred during: "Java Search"
Summary: [search] An internal error occurred during: "Java Search"
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 3.7 M2   Edit
Assignee: Satyam Kandula CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2010-05-21 08:29 EDT by Kai CLA
Modified: 2011-01-25 12:30 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kai CLA 2010-05-21 08:29:08 EDT 
Build Identifier: M20100211-1343

when selectting the name of a method and searching for its references in the java project i'll receive the error: An internal error occurred during: "Java Search"

i'm working with eclipse (64bit edition) on windows server 2k8 r2 64bit.

the same error message is been described in the fixed bug #281317

but the stacktrace there is different from mine:

eclipse.buildId=M20100211-1343
java.version=1.6.0_20
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_CH
Command-line arguments:  -os win32 -ws win32 -arch x86_64


Error
Fri May 21 14:14:26 CEST 2010
An internal error occurred during: "Java Search".

java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at org.eclipse.jdt.internal.compiler.util.ObjectVector.copyInto(ObjectVector.java:87)
at org.eclipse.jdt.internal.core.search.matching.PossibleMatchSet.getPossibleMatches(PossibleMatchSet.java:51)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1068)
at org.eclipse.jdt.internal.core.search.matching.MatchLocator.locateMatches(MatchLocator.java:1210)
at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.locateMatches(JavaSearchParticipant.java:94)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:223)
at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:507)
at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:551)
at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.run(JavaSearchQuery.java:144)
at org.eclipse.search2.internal.ui.InternalSearchUI$InternalSearchJob.run(InternalSearchUI.java:91)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)



Reproducible: Always
Comment 1 Dani Megert CLA 2010-05-21 08:36:29 EDT 
Can you provide a test case / project? Similar issue is discussed in bug 23211.
Comment 2 Satyam Kandula CLA 2010-06-09 02:39:04 EDT 
Can you give the classpath (the file .classpath) of your projects? I think some duplicates in the classpath could cause this behavior.
Comment 3 Satyam Kandula CLA 2010-07-13 05:03:58 EDT 
Are you still running into this problem? I believe that there is some problem with the classpath. Can you give the classpath of the projects?
Comment 4 Kai CLA 2010-10-26 05:26:23 EDT 
Thanks for the hint with the duplicate entries in classpath. 
That was it.
Comment 5 Olivier Thomann CLA 2011-01-25 12:30:24 EST 
Verified.