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.
| Summary: | [69cat] AWT thread blocked for 21063 ms. | ||
|---|---|---|---|
| Product: | webservices | Reporter: | Exceptions Reporter <exceptions_reporter> |
| Component: | Manager | Assignee: | Denis Anisimov <ads> |
| Status: | RESOLVED FIXED | ||
| Severity: | blocker | CC: | hmichel, misterm, roger_rf |
| Priority: | P3 | Keywords: | PERFORMANCE, REGRESSION |
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://statistics.netbeans.org/exceptions/detail.do?id=157446 | ||
| Issue Type: | DEFECT | Exception Reporter: | 157446 |
| Attachments: | nps snapshot | ||
|
Description
Exceptions Reporter
2009-09-19 02:06:43 UTC
Created attachment 87944 [details]
nps snapshot
This issue already has 6 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157446 SaasNodeChildren should initialize immediately or be asynchronous. In the snapshot initialization takes > 20s. This issue already has 8 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157446 The snapshots lead to websvc.manager code. *** Issue 173070 has been marked as a duplicate of this issue. *** This issue already has 14 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=157446 As my latest (275393 and some others) posts, I just can't change the selected file in Projects view. I consider it an regression and just can be found at latest build 200910071536. The build 200910070250 doesn't has this regression. I decreased the priority since I just removed my indexes and it looks it like is working again. BTW, I added new comments at report and looks like the component and subcomponent are incorrect here. The problem is inside websvc.saas.api module. The stacktrace of the problem starts from SaasNodeChildren class ( websvc.saas.ui) and its method addNotify() which calls toStateReady( false ) of Saas class . The last one is overridden by WsdlSaas method. The parameter value "false" means that call should be performed asynchronously which should prevent UI freeze. But there is no special logic which handles asynchronous essence . The problem of the attached nps file is call WsdlUtil.getWsdlData() which asks WSDL model . It has parameter for asynchronous call but implementation ignores this parameter. But WsdlSaas.toStateReady() implementation logic is still badly written because even WsdlUtil.getWsdlData() implementation is correctly written respectively asynchronous call its return value cannot be used for further work in the caller thread. All further work should be done after notification of finished task. So actually either - there is no need in asynchronous call of WsdlUtil.getWsdlData() and toStateReady() method should put all its code into dedicated thread in case of asynchronous request or - WsdlUtil.getWsdlData() should be implemented correctly according asynchronous parameter value and logic of toStateReady() should be rewritten respectively. It's too risky to fix this bug for the upcoming release. Should be fixed in the next release. changeset: 192950:fb3f88ee9b22 Integrated into 'main-golden', will be available in build *201104290000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/fb3f88ee9b22 User: Denis Anisimov <ads@netbeans.org> Log: Fix for BZ#172592 - [69cat] AWT thread blocked for 21063 ms. |