Re: [wtp-dev] "java indexing" thread causes high cpu load after build

[NICHOLAS SANDONATO <nsandona@xxxxxxxxxx>]

Hi Patric,

Please feel free to open an enhancement
request: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=WTP%20Source%20Editing&component=jst.jsp

- Nick

From:	Patric Rufflar <patric@xxxxxxxxxxx>
To:	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Date:	03/15/2011 11:28 AM
Subject:	Re: [wtp-dev] "java indexing" thread causes high cpu load after build
Sent by:	wtp-dev-bounces@xxxxxxxxxxx

---

Hi Nicolas,

thank you for your answer.
Filtering some files because of some rules (e.g. derived state) would  
be very cool.
Should I log an enhancement request?

Btw: I locally changed the WTP sources to not consider derived  
ressources using the PDE.
How can I create a patched plugin/feature patch to make these changes  
persistent and to share them with my colleagues?

Best regards,
Patric




Quoting NICHOLAS SANDONATO <nsandona@xxxxxxxxxx>:

> Hi Patric,
>
> This indexing of JSPs is so that Java references in them can be used
for
> search and refactoring.  Right now, there is no way to disable
this
> indexing as it potentially removes a lot of functionality.  The
preference
> to include JSP matches in Java searches pertains only to the reporting
in
> the view and not to the actual indexing of these files.  We would
likely
> be able to enhance the indexer to ignore particular files based on
some
> rules like if it's derived.
>
>
>
>
> From:
> Patric Rufflar <patric@xxxxxxxxxxx>
> To:
> wtp-dev@xxxxxxxxxxx
> Date:
> 03/11/2011 12:43 PM
> Subject:
> [wtp-dev] "java indexing" thread causes high cpu load after
build
> Sent by:
> wtp-dev-bounces@xxxxxxxxxxx
>
>
>
> Hello,
>
> I am experiencing the reproducible problem that
> the java indexing thread causes high cpu load for several minutes
> after a build took place.
>
> My build procedure includes a special builder which (more or less)
> copies all jsps to another directory in my project (and marks these
> copies as derived).
>
> All Web/WTP validators are configured as suspended in the preference
> dialog.
>
> Please have a look at the following thread dump which has been taken
> after a build finished and while the cpu usage can be seen:
> (although I cannot see any active background tasks in the progress
> monitor)
>
> org.eclipse.jst.jsp.core.internal.parser.internal.JSPTokenizer.primGetNextToken()
> (line:
> 2120)
> org.eclipse.jst.jsp.core.internal.parser.internal.JSPTokenizer.getNextToken()
>
> (line: 1643)
> org.eclipse.wst.xml.core.internal.parser.XMLSourceParser.getNextRegion()
> (line: 189)
> org.eclipse.jst.jsp.core.internal.parser.JSPSourceParser.parseNodes()
> (line: 237)
> org.eclipse.wst.xml.core.internal.parser.XMLSourceParser.getDocumentRegions()
>
> (line: 173)
> org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser._core_reparse_text(int,
>
> int)
> org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser.core_reparse(int,
> int, org.eclipse.wst.sse.core.internal.text.CoreNodeList, boolean)
(line:
> 710)
> org.eclipse.jst.jsp.core.internal.parser.JSPReParser.reparse(org.eclipse.wst.sse.core.internal.provisional.text.IStructuredDocumentRegion,
> org.eclipse.wst.sse.core.internal.provisional.text.IStructuredDocumentRegion)
> (line:
> 143)
> org.eclipse.wst.sse.core.internal.text.StructuredDocumentReParser.reparse()
>
> (line: 1291)
> org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.updateModel(java.lang.Object,
> int, int, java.lang.String) (line:
> 2709)
> org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(java.lang.Object,
> int, int, java.lang.String, long, boolean) (line:
> 1923)
> org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(java.lang.Object,
> int, int, java.lang.String, long, boolean) (line:
> 2419)
> org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.setText(java.lang.Object,
> java.lang.String) (line:
> 2606)
> org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.setText(java.lang.Object,
> java.lang.String) (line:
> 188)
> org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.set(java.lang.String)
> (line:
> 2481)
> org.eclipse.jst.jsp.core.internal.java.XMLJSPRegionHelper.parse(java.lang.String)
> (line:
> 159)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslator.handleIncludeFile(java.lang.String)
> (line:
> 2310)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateDirective(java.util.Iterator)
> (line:
> 2033)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateJSPNode(org.eclipse.wst.sse.core.internal.provisional.text.ITextRegion,
> java.util.Iterator, java.lang.String, int) (line:
> 1766)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translateRegionContainer(org.eclipse.wst.sse.core.internal.provisional.text.ITextRegionCollection,
> int) (line:
> 1349)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslator.translate() (line:
> 1127)
> org.eclipse.jst.jsp.core.internal.java.JSPTranslationAdapter.getJSPTranslation()
> (line:
> 153)
> org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getJSPTranslation()
> (line:
> 120)
> org.eclipse.jst.jsp.core.internal.java.search.JSPSearchDocument.getCharContents()
> (line:
> 77)
> org.eclipse.jst.jsp.core.internal.java.search.JavaSearchDocumentDelegate.getCharContents()
> org.eclipse.jdt.internal.core.search.indexing.SourceIndexer.indexDocument()
>
> (line: 60)
> org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(org.eclipse.jdt.core.search.SearchDocument,
> org.eclipse.core.runtime.IPath) (line:
> 72)
> org.eclipse.jst.jsp.core.internal.java.search.JSPSearchParticipant.indexDocument(org.eclipse.jdt.core.search.SearchDocument,
> org.eclipse.core.runtime.IPath) (line:
> 72)
> org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(org.eclipse.jdt.core.search.SearchDocument,
> org.eclipse.jdt.core.search.SearchParticipant,
> org.eclipse.jdt.internal.core.index.Index, org.eclipse.core.runtime.IPath)
> (line:
> 453)
> org.eclipse.jdt.internal.core.search.indexing.IndexManager$1.execute(org.eclipse.core.runtime.IProgressMonitor)
> (line:
> 853)
> org.eclipse.jdt.internal.core.search.processing.JobManager.run() (line:
> 404)
> java.lang.Thread.run() (line: 662)
>
>
> "Include JSP matches in Java searches" is disabled.
> I am using the most recent Eclipse 3.6.2 / WTP 3.2.3
>
> My questions:
> - What does this java indexing do in my case?
> - Is this is bug? Or did I miss an important configuration option?
> - Is there a workaround? Can I disable this indexing or at least for
> all derived files?
>
> Thank you and best regards,
> Patric
>
>
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev
>
>
>




_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev