Community
Participate
Working Groups
-- Error Log -- Date: Tue Aug 28 16:36:44 BST 2007 Message: Background Indexer Crash Recovery Severity: Error Plugin ID: org.eclipse.jdt.core Stack Trace: java.lang.IllegalArgumentException: Document path **path unknown** must be relative to **path unknown** at org.eclipse.jdt.internal.core.index.Index.containerRelativePath(Index.java:103) at org.eclipse.jdt.internal.core.search.indexing.InternalSearchDocument.getContainerRelativePath(InternalSearchDocument.java:32) at org.eclipse.jdt.internal.core.search.indexing.InternalSearchDocument.removeAllIndexEntries(InternalSearchDocument.java:40) at org.eclipse.jdt.core.search.SearchDocument.removeAllIndexEntries(SearchDocument.java:128) at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(JavaSearchParticipant.java:68) at org.eclipse.jst.jsp.core.internal.java.search.JSPSearchParticipant.indexDocument(JSPSearchParticipant.java:72) at org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(IndexManager.java:314) at org.eclipse.jdt.internal.core.search.indexing.IndexManager$1.execute(IndexManager.java:658) at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:392) at java.lang.Thread.run(Thread.java:619)
Could you please provide: - build ID - steps to reproduce ? Thanks.
Build id is: Build id: I20070621-1340 I'll attach eclipse config log. Rough steps to trigger are: 1) Open closed project 2) Let it index for a while 3) Close I can retest but it's not repeatable as far as I know. My log also shows a number of JSPIndexer problems.
Created attachment 77146 [details] eclipse config dump
If you go into this folder (inside your workspace root) .metadata\.plugins\org.eclipse.jdt.core, you should find a bunch of .index files. If you remove them and restart Eclipse, the indexer will create them again. If they are there, it doesn't create them again. So if you delete them and on the next restart, you get the same problem, it could be useful for us to get your project.
Tried deleting the index files. Played around a bit opening and closing that project, no luck in repeating it.
Can you attach the log to let us see the JSPIndexer problems, then I can decide whether this bug should be moved to WebTools/jst.jsp component, thanks
Created attachment 77236 [details] log of JSP indexer problems Note that these are not the JSP indexer errors from the original bug report, but from a later test where I was able to repeat this problem (but not the JDT index error).
Thanks for the feedback. Move to WebTools/jst.jsp component for further investigation as the origin seems to be a NPE while getting document path...
*** Bug 216938 has been marked as a duplicate of this bug. ***
It would seem from the log file that the index attempted to access a bunch of jsp files that no longer existed, probably because the project was closed. Then once the project was opened again there was some issue with the JSPTranslator. Part of me says this one maybe worth digging into a bit and seeing if there are now protections in place to protect against this but the rest of me is thinking that if for the past 2 years whenever a project with a bunch of JSPs was closed and opened a bunch of logged error messages occurred then we would know about it. End opinion is this one deserves a bit of investigation but without information there is not much luck in anything coming from it.