This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build 200911091156) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows XP, 5.1, x86 User Comments: stefan79: Inspect Members jsedek: I just opened persistence.xml file aquaglia: Generating JAP 2.0 Entities kcundick: Just starting NetBeans up. j0ni: opening a project. GUEST: Openning persistence.xml file GUEST: running a few jUnit tests GUEST: junit tests with a failure, double clicking on stacktrace at "Test Results" window GUEST: Starting NetBeans, three projects in the workspace. Maximum slowness yet reported was 6640 ms, average is 4241
Created attachment 90772 [details] nps snapshot
This issue already has 21 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=158084
While asking for javadoc it ends in native calls (opening jar file). I can't do anything with it in filesystems.
This issue already has 22 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=158084
Let's talk about http://statistics.netbeans.org/exceptions/exception.do?id=298197 It is clear that glassfish javaee code is using RequestProcessor.getDefault improperly. The org.netbeans.modules.glassfish.javaee.JavaEEServerModuleFactory.ensureGlassFishApiSupport() shall run once (at most). Not four times in parallel. Let's try to fix this. Then probably reassign back, I'll find another person to fix something.
I do not see any gf code in the nps that you pointed at... http://statistics.netbeans.org/exceptions/exception.do?id=298197 Please let me know which nps you want me to look at.
You need to open the NPS file in NetBeans! Seek for "ensureGlassFishApiSupport" then. You will find four occurences which is about four times more than you shall find.
okay.
these two commits may help... http://hg.netbeans.org/web-main/rev/692a7601ad69 http://hg.netbeans.org/web-main/rev/e1a9ce21afe6 let me know
This issue already has 24 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=158084
Integrated into 'main-golden', will be available in build *200911160201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/692a7601ad69 User: Vince Kraemer <vkraemer@netbeans.org> Log: #176486: prevent over initialization
push back to a product/camponent that Jaroslav might see... in case he is looking at the dashboard instead of doing an 'assigned to' query...
Vince, your commits are like black magic. A little touch here, a little change there and let's pray the behaviour will be better. I have little trust the behaviour will improve using this style of development. I have asked the glassfish team to stop using RequestProcessor.getDefault(), as that does not seem appropriate for your usecase. Why can't you just read javadoc of RequestProcessor, and rewrite your code to use named RequestProcessor with throughput one? That is not that hard and you would eliminate the parallel execution of ensureGlassFishApiSupport entirely without suspicious and magical preferences mangling. Please study the RequestProcessor javadoc, change your code and assign back to me.
OK. A quick grep shows 55 uses in 39 files. That seems like something that I will need to request a waiver for.
The initial issue that prompted Jaroslav to assign this issue to me has been dealt with. See https://netbeans.org/bugzilla/show_bug.cgi?id=176486#c9. He has raised some additional requirements on this before I can close the issue or transfer it back to him. Those changes (audit the team's code and replace RequestProcessor.getDefault() with a named RequestProcessor) could be broad ranging and destabilizing at this point.
There have been two reports of this slowness from builds created after 2009-11-14 (which is when my fix went into the trunk): 318543 and 321929... I have looked through both and they appear to be related to the form editor. So, I am going to reassign this issue to the form editor...
Don't know why the two last snapshots appeared under this report - they represent another issue (already fixed in GUI builder), I've moved them there: http://statistics.netbeans.org/exceptions/detail.do?id=154265
good to know. marking as fixed