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.
Profiler 070327 NetBeans IDE Dev (Build 200703272330) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Sun Java System Application Server 9.1 (build b33) There are no exact steps on how to reproduce this issue. I was performing OrderSystem (http://www.netbeans.org/nonav/issues/showattachment.cgi/37566/order_system.zip) testing on GlassFish server using Start in Profile Mode, then direct attach, then detach not stopping the application and then dynamic attach. Then detach and dynamic attach again. All the attempts were about CPU profiling with different parameters. After several attempts I got a Profiled application is not responding message. When I agreed to stop profiling the IDE became frozen. The same time profiled application was working on server, as well as many of Admin Console features connected with deployed applications and resources while the part of Admin Console linked with Application Server properties and VM setting was not responding.
Created attachment 40109 [details] Part of IDE log and thread dump
This seems like a kind of distributed deadlock - the application is locked waiting for the results from the server. For further investigation the server threaddump is necessary
NB 6.0 200704061800 & GF v2 Build50, yesterday I get in a similar situation on while profiling a project on windows xp and solaris 10-sparc. On the windows host could not get the threads dump of the IDE using stacktrace (the host was very painfully responding - connected with rdesktop - and was obliged to kill the java processes using the Task Manager). But on the solaris-sparc it was much easier to get the stack : kill -QUIT I'm adding the IDE threads-dump in the attachement taken before closing the IDE window (right top x). Also, I'll try to do the threads-dump of the server. nouar (I'm helping the serverpluging team in testing nb 6.0).
Created attachment 43595 [details] solaris 10 sparc T1000 (jdk 1.6u1) IDE deadlock
thanks for the thread dump the server part is not required :) the deadlock is caused by accessing AWT component tree outside of the AWT thread.
Created attachment 43598 [details] server.log for domain1 on solaris10
Created attachment 43599 [details] join threads dumps for profiler process solaris 10-sparc
Created attachment 43600 [details] join threads dump for server done with jstack
sorry nouar, what you submitted in fact belongs to the issue #105508. i'll attach your comments and dumps there
ok thanks, did not get notified before submitting the different attachments. I'll follow on the other issue. have a nice day. nouar,
this should be fixed with the issue #82357 the fix addresses deadlock caused by calling the "forceObtainedResults" method
Verified with Beta1