Community
Participate
Working Groups
After approximately an hour of normal eclipse usage (including search, opening types using the Open Type dialog, and refactoring), my search indexer will hang, causing components dependent on indexing to also hang. I can cancel the indexer task, but the next time I try and use a search function, the process begins again and then hangs with the same number of files left to index. Attempting to close eclipse will display the "Saving Workspace" dialog, which will run to completion and then close, but the javaw.exe process will remain running with 0% CPU utilization in the background. The problem usually manifests within about an hour of use, but occasionally takes longer to show. I upgraded to 3.2M4, but also see this same problem. I am running Eclipse+WTP+GEF+EMF+JEM for the 3.1.1 stream, and have a number of JSP's in my workspace (the JSP indexer is running periodically, but I don't see it hanging the same way I see the standard indexer hanging).
Created attachment 33394 [details] Screen capture of the progress bar after running a search Once the problem manifests, any search will pause at the beginning waiting for indexing to complete (which never happens). The search can be cancelled normally, and the background indexing job can be cancelled normally, but the next time I search another background indexing job starts which also hangs.
Created attachment 33395 [details] Image of the hung progress task After cancelling a hung search task, this is a screencap of the hung indexer task. Taken from eclipse 3.2M4, but looks similar in 3.1.1
The workspace this is occuring in has been created from scratch twice. It is about 30-40 java projects (exporting 1-5 jar files each), and a single java project that is essentially running against an installed Websphere Appserver 6 WAR file. The project was created in the root WAR directory and the java source is being compiled out of and back into WEB-INF/classes with WAS running in the background (and class-reloading active). It is possible that WAS and eclipse are competing for file locks on the source java files or generated class files in this directory. However, full recompilations and incremental recompilations have never failed to complete before and I have not noticed any strange behavior that might indicate file locking is an issue. Plus, I would assume the Java Indexer is indexing the .java files which should not be in contention.
Could you make a VM snapshot, put output in a file and attach it to this bug? Thx
Created attachment 33476 [details] Java core dump taken in 3.2M4 when the indexer hangs core dump taken in 3.2M4 when the indexer hangs
We have the same problem, but only with the IBM JDK. Probably the same JDK that the reporter is using (as far as I can say from looking at the core dump and checking my Eclipse configuration: "java.fullversion=J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc)")
Ping'ed the IBM J9 team.
Clayton / Victor : would there be anything relevant in the .log file ? If the indexer was constantly failing to index, it may retry forever maybe...
The ".log" file (in my eclipse workspace under ".metadata") contains nothing suspicious. The last entry is from 13:58 (now it is 18:36) and the indexing problem is back: trying to open a type displays "refeshing indexes 0%" without any progress. If I now close Eclipse, I have to explicitely kill the javaw.exe. If not, Eclipse will say that the workspace is still in use.
3.2 Release version shows the similar symptom as well
Clayton / Victor: Do you still have this issue? If so, can you let me know if you're using WTP or any other plugins/product on top of eclipse SDK? Can you also make a try with a more recent version of IBM J9 VM if one exist? Thanks
As there's nothing in the .log, I currently assume that this freeze of indexing job is a VM issue...
