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 149913 - "Enterprise Beans" node in project window freezes NB
Summary: "Enterprise Beans" node in project window freezes NB
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrey Yamkovoy
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2008-10-13 08:58 UTC by witoldsz
Modified: 2009-10-06 13:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
4 thread dumps taken during waiting for 'Enterprise Beans' node to appear. (17.49 KB, application/x-compressed)
2008-10-13 22:48 UTC, witoldsz 		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 witoldsz 2008-10-13 08:58:44 UTC 
Hi there,
when working on my EJB project (+/- 80 EJBs) when I click "Enteprise Beans" node in project window, NetBeans takes 100%
CPU for... I don't know exactly but something like one minute or maybe less. During that period entire IDE is not
responding. This happens only at the first time, I mean when I close this node and open it again, it is cached and opens
quickly. 
If this operation is really so much time-consuming (maybe it could be optimized) I think it should spawn a background
thread instead of freezing everything.
Comment 1 David Konecny 2008-10-13 21:59:10 UTC 
Could you please try to reproduce again on your PC and follow http://wiki.netbeans.org/GenerateThreadDump to generate
two or three thread dumps when IDE is not responding and attach then to this issue for evaluation. Thanks.
Comment 2 witoldsz 2008-10-13 22:48:54 UTC 
Created attachment 71701 [details]
4 thread dumps taken during waiting for 'Enterprise Beans' node to appear.
Comment 3 David Konecny 2008-10-14 00:18:21 UTC 
Thanks for the thread dumps. It does look like EJB node is waiting on Java parsing infrastructure to draw itself.
Perhaps that should be done lazily on background. Passing to EJB guys to evaluate.
Comment 4 Andrey Yamkovoy 2009-10-06 13:16:12 UTC 
Already fixed by collecting EJBs lazily on background and showing node Scanning for EJBs ...