Created attachment 78829 [details]
thread dump

The thread with GF code is blocked and doesn't appear to be holding any locks that would contribute to a problem in the
AWT thread...

I am puzzled by three threads that are waiting and locking on 0xafeba5d0...  "Default RequestProcessor", "Find Modules"
and "AWT-EventQueue-1"...

There may be a conflict between j2eeserver, ergonomics and autoupdate, though....

OK, so reassign to ergonomics for evaluation 

 at org.openide.util.lookup.ProxyLookup.lookup(ProxyLookup.java:205)
 at o.n.m.j2ee.deployment.impl.Server.<init>(Server.java:117)
 at o.n.m.j2ee.deployment.impl.ServerRegistry.addPlugin(ServerRegistry.java:179)
	- locked <0xb0f3e588> (a o.n.m.j2ee.deployment.impl.ServerRegistry)

vs.

 at o.n.m.j2ee.deployment.impl.ServerRegistry.getServerInstance(ServerRegistry.java:294)
	- waiting to lock <0xb0f3e588> (a o.n.m.j2ee.deployment.impl.ServerRegistry)
 at o.n.m.j2ee.deployment.plugins.api.InstanceProperties.getInstanceProperties(InstanceProperties.java:152)
 at o.n.m.glassfish.javaee.JavaEEServerModuleFactory.createModule(JavaEEServerModuleFactory.java:107)
 at o.n.m.glassfish.common.GlassfishInstance.updateModuleSupport(GlassfishInstance.java:157)
 at o.n.m.glassfish.common.GlassfishInstance.<init>(GlassfishInstance.java:125)
 at o.n.m.glassfish.common.GlassfishInstance.create(GlassfishInstance.java:196)
 at o.n.m.glassfish.common.GlassfishInstanceProvider.registerDefaultInstance(GlassfishInstanceProvider.java:585)
 at o.n.m.glassfish.common.GlassfishInstanceProvider.<init>(GlassfishInstanceProvider.java:171)
 at o.n.m.glassfish.common.GlassfishInstanceProvider.getPrelude(GlassfishInstanceProvider.java:118)
 at o.n.m.glassfish.common.wizards.GlassfishWizardProvider.createPrelude(GlassfishWizardProvider.java:56)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

What can we do about that?

Can we delay following code in GlassfishInstanceProvider:

        try {
            registerDefaultInstance();
            loadServerInstances();
        } catch(RuntimeException ex) {
            getLogger().log(Level.INFO, null, ex);
        }

to be done lazily and not in the constructor of the provider? Will that help?

I think instance should not be loaded directly when creating the provider. Is there a reason for that? Vince can you fix
it - load instances lazily? Imo it would also solve issue 160579.

what do you mean by lazily?

There is a typo in previous post - (server) instances should be loaded lazily.

I mean when they are really needed - on the first call to getInstances(), not when the provider is instantiated.

likely fixed by http://hg.netbeans.org/web-main/rev/55b6b94e9165

http://hg.netbeans.org/main-golden/rev/55b6b94e9165

v.
NetBeans IDE Dev (Build web-main-465-on-090424)