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.
Created attachment 135040 [details] deadlock info Starting NetBeans while viewing the Services Window and clicked the Server node. NetBeans is deadlocked and won't finish starting. See attached files.
Created attachment 135041 [details] logfile
Probably related to GlassFish. Please evaluate. Thank you.
Unfortunately this is not thread dump with lock IDs. I need locks to see cycle in locks dependency. Did you see this more than once? If so, please provide full Java VM thread dump. You can make it by sending signal 3 (SIGQUIT) to java process when it's in deadlock on UNIX systems. But I have no idea how to do this on windows. Switching to incomplete until having thread dump with locks.
(In reply to comment #3) > Unfortunately this is not thread dump with lock IDs. I need locks to see cycle > in locks dependency. You need just source code and careful evaluation. Obviously the deadlock is between Node.INIT_LOCK and GlassfishInstance.lookupResult.
I can't reproduce it to get a thread dump or I would get you one.
Do you think this could have anything to do with JavaEE magically self deactivating when NetBeans starts up? There is a problem when changing things in Options--anywhere in options--and using the new Apply Button that when after using it, PHP or C/C++ (or both) are deactivated on restart. Today, on the latest Dev Build, I have JavaEE self deactivating when I restart NetBeans. It doesn't do it every time, but what I do is: 1. change Keyboard profile to Eclipse 2. and then change to a new L&F theme. Click Apply and then OK 3. and then click the link on the Notification to restart NetBeans. Then when it restarts, PHP, C/C++ and JavaEE is deactivated. Sometimes just PHP and C/C++. Then when I click the server link, the 2 GlassFish instances are gone because JavaEE was deactivated. Product Version: NetBeans IDE Dev (Build 201307232300) Updates: Updates available Java: 1.7.0_25; Java HotSpot(TM) 64-Bit Server VM 23.25-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_25-b16 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Well I didn't know until now that the full distribution would automatically disable modules if they were not used, so that explains Comment 3 as to why they are being disabled. Please ignore Comment 3.
This should be fixed with Bug# 236031 fix. Code paths that are causing deadlock are almost the same and the same methods are being involved here. MArking as 236031 duplicate. *** This bug has been marked as a duplicate of bug 236031 ***