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.

Bug 180542 - MainProjectAction body run in EQ
Summary: MainProjectAction body run in EQ
Status: RESOLVED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
: 207433 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-10 06:58 UTC by Exceptions Reporter
Modified: 2013-06-27 02:17 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 165073

Attachments
nps snapshot (256.00 KB, application/nps)
2010-02-10 06:58 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2010-02-10 06:58:50 UTC 
Build: NetBeans IDE Dev (Build web-main-2366-on-100114)
VM: Java HotSpot(TM) 64-Bit Server VM, 14.3-b01-101, Java(TM) SE Runtime Environment, 1.6.0_17-b04-248-9M3125
OS: Mac OS X

User Comments:
pjiricka: Run web application on WebLogic.



Maximum slowness yet reported was 12589 ms, average is 12589
Comment 1 Exceptions Reporter 2010-02-10 06:58:56 UTC 
Created attachment 94039 [details]
nps snapshot
Comment 2 Tomas Zezula 2010-02-10 07:03:24 UTC 
Setting P2 according to pjiricka.
Comment 3 David Konecny 2010-02-18 15:29:25 UTC 
There seems to be several unrelated exception reports. One group of them contain WebActionProvider.isEjbRefAndNoJ2eeApp() and these can be ignored as that was resolved a while ago. Then there was slow report where parsing was blocking Nodes operation - I moved that one to nodes for evaluation. There is couple of reports, like one from pjiricka which ends in ant module taking too much time to run targets. I don't know why so I'm passing to Ant module. I do not think this is P2 anymore as it will take a time to stabilize WebLogic integration.
Comment 4 Jesse Glick 2010-03-11 13:15:13 UTC 
Project actions could probably run on another thread. (It takes a bit of time to prepare the Ant process and output window tab; usually not nearly this long, so something else was wrong but I don't know what.)
Comment 5 Jesse Glick 2010-04-13 00:58:30 UTC 
Careful; see bug #178848.
Comment 6 Jesse Glick 2010-05-14 20:59:21 UTC 
Probably too risky for 6.9.
Comment 7 Jesse Glick 2012-01-19 23:04:42 UTC 
*** Bug 207433 has been marked as a duplicate of this bug. ***
Comment 8 Milos Kleint 2013-06-21 07:14:29 UTC 
posting MainProjectAction.actionPerformed to RP seems safe, however renders the tests we have useless. 

same applies to ProjectAction and FileAction subclasses of LookupSensitiveAction.

Please note that sometimes not only the performer is slow but even getting projects from context lookup (via FileOwnerQuery)
Comment 9 Milos Kleint 2013-06-21 07:23:54 UTC 
related/duplicate to issue 177959
Comment 10 Milos Kleint 2013-06-24 13:37:27 UTC 
http://hg.netbeans.org/core-main/rev/f2927475bfa1
Comment 11 Quality Engineering 2013-06-27 02:17:11 UTC 
Integrated into 'main-golden', will be available in build *201306262301* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/f2927475bfa1
User: Milos Kleint <mkleint@netbeans.org>
Log: #180542, #188382, #213607, #177959 actionPerformed() in lookupSensitiveAction subclasses posted to RP. In tests kept in AWT to avoid deleting them altogether. Might have problems primarily with lookup content changing between AWT and RP processing.