Build: NetBeans IDE Dev (Build 200908022240)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Windows XP, 5.1, x86
misterm: Opening project node for freeform project
Maximum slowness yet reported was 21063 ms, average is 8565
Created attachment 87944 [details]
This issue already has 6 duplicates
SaasNodeChildren should initialize immediately or be asynchronous. In the snapshot initialization takes > 20s.
This issue already has 8 duplicates
The snapshots lead to websvc.manager code.
*** Issue 173070 has been marked as a duplicate of this issue. ***
This issue already has 14 duplicates
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
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
- 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
Integrated into 'main-golden', will be available in build *201104290000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Denis Anisimov <email@example.com>
Log: Fix for BZ#172592 - [69cat] AWT thread blocked for 21063 ms.