Eclipse (Kepler) Workspace acts weird (type hierarchy, link search not working)

Question

Using Eclipse Kepler Works on Windows 7 (64-bit), my workspace is acting weird.

Doesn't work (workspace):

• The hierarchy of class / method types is displayed empty.
• search links

Have tried

• Recovery / cleaning / closing and opening projects
• Restart Eclipse
• Reboot
• Download Eclipse in cleanup mode (-clean)
• Clear indexes manually

the only thing that has worked so far is the transition to a new workspace and checking out one of my projects. However, this is very suboptimal, since I have a certain number of projects and settings in my current workspace.

EDIT - Stack Trace

I get the following stack trace when I specifically "Focus On" in the "Hierarchy Type" view:

!ENTRY org.eclipse.core.jobs 4 2 2013-12-19 15:08:39.156 !MESSAGE An internal error occurred during: "Computing type hierarchy of 'String - java.lang'...". !STACK 0 java.lang.NullPointerException at org.eclipse.core.runtime.Path.<init>(Path.java:183) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:182) at org.eclipse.jdt.internal.core.JavaModel.getJavaProject(JavaModel.java:189) at org.eclipse.jdt.internal.core.search.IndexSelector.getJavaProject(IndexSelector.java:286) at org.eclipse.jdt.internal.core.search.IndexSelector.initializeIndexLocations(IndexSelector.java:217) at org.eclipse.jdt.internal.core.search.IndexSelector.getIndexLocations(IndexSelector.java:276) at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.selectIndexURLs(JavaSearchParticipant.java:121) at org.eclipse.jdt.internal.core.search.PatternSearchJob.getIndexes(PatternSearchJob.java:84) at org.eclipse.jdt.internal.core.search.SubTypeSearchJob.getIndexes(SubTypeSearchJob.java:33) at org.eclipse.jdt.internal.core.search.PatternSearchJob.ensureReadyToRun(PatternSearchJob.java:52) at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:174) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.searchAllPossibleSubTypes(IndexBasedHierarchyBuilder.java:523) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.determinePossibleSubTypes(IndexBasedHierarchyBuilder.java:406) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build(IndexBasedHierarchyBuilder.java:120) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute(TypeHierarchy.java:300) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh(TypeHierarchy.java:1267) at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation(CreateTypeHierarchyOperation.java:90) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:918) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:876) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.createTypeHierarchy(TypeHierarchyLifeCycle.java:299) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefresh(TypeHierarchyLifeCycle.java:330) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefreshBackground(TypeHierarchyLifeCycle.java:271) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$2.run(TypeHierarchyLifeCycle.java:224) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) 

Is anyone

Answer 1

Found a problem.

For some reason, I had a corrupt resource in one of my projects. It did not appear in the package tree, but it appeared in the error log in Eclipse as

Error creating link for external folder X: \ somefolder

After checking each project (because the error did not point to one), I really found this resource in one of the build paths (in the Configure Build Path menu, where it displayed the error icon!) And deleted it.

Now everything works again!

Thanks to everyone for the answer / comment. Publishing this for future developers is experiencing the same problem.

Lesson learned: do (extensively) check the Eclipse error log!