This issue was originally marked as duplicate of issue 171690, that is already resolved. This issue is still valid, so this seems to be another issue, but it might be related.
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 7, 6.1, x86
aschild: Listing all RESTful Web Services in the project overview
Maximum slowness yet reported was 11660 ms, average is 11660
Created attachment 90767 [details]
RestServicesChildren.createNodes() is called from AWT, and (indirectly) touches the Java infrastructure. I guess that the nodes should be created on background, showing a wait cursor.
Instead of usage RestServicesChildren as Children.Keys one need to realize
children via ChildFactory.
Current implementation of RestServicesChildren class tries to implement
functionality which can be done via usage of Children.create() and
The current implementation puts keys initialization into dedicated thread.
As result createNodes() method should not spend too much time in AWT because
Rest Service model is already initialized . As result any further access to
this model ( after its initialization ) is not so time consuming.
And method createNodes() is not a problem here.
The problem is inside method addNotify() which could start model initialization
( method getModel() could be the problem because it is based on Java infrastructure ).
So I suggest to put all Rest Service model access into asynchronous call
which can be done inside createKeys() method of ChildFactory implementation
user: Denis Anisimov <firstname.lastname@example.org>
date: Wed Oct 27 11:17:24 2010 +0400
summary: Fix for BZ#176481 - AWT thread blocked for 11660 ms.
Integrated into 'main-golden', will be available in build *201010280000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Denis Anisimov <email@example.com>
Log: Fix for BZ#176481 - AWT thread blocked for 11660 ms.