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.
| Summary: | Deadlock when creating web project | ||
|---|---|---|---|
| Product: | db | Reporter: | Jiri Skrivanek <jskrivanek> |
| Component: | Derby | Assignee: | Libor Fischmeistr <lfischmeistr> |
| Status: | NEW --- | ||
| Severity: | normal | Keywords: | RANDOM, THREAD |
| Priority: | P3 | ||
| Version: | 7.1 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | Thread dump. | ||
This actually reads like a derby and db plugins issue...
org.netbeans.modules.derby.DerbyActivator.activate(DerbyActivator.java:71)
- locked <0x213b2e98> (a java.lang.Class for org.netbeans.modules.derby.DerbyActivator)
holds the lock that
at org.netbeans.modules.derby.DerbyActivator.activate(DerbyActivator.java:67)
- waiting to lock <0x213b2e98> (a java.lang.Class for org.netbeans.modules.derby.DerbyActivator)
wants AND
at org.netbeans.modules.derby.RegisterDerby.getDefault(RegisterDerby.java:101)
- locked <0x213b2f10> (a java.lang.Class for org.netbeans.modules.derby.RegisterDerby)
holds the lock that
at org.netbeans.modules.derby.RegisterDerby.getDefault(RegisterDerby.java:99)
- waiting to lock <0x213b2f10> (a java.lang.Class for org.netbeans.modules.derby.RegisterDerby)
wants...
The GF plugin started one of these threads but is deep in the stack and far from holding any of the locks that are participating in this deadlock.
forgot to switch comp/subcomp... No changes in this core during 7.1 cycle, anyway it should be fixed ASAP. |
Created attachment 113702 [details] Thread dump. Product Version: NetBeans IDE 7.1 RC2 (Build 201111302200) Java: 1.7.0_02; Java HotSpot(TM) Client VM 22.0-b10 System: Windows XP version 5.1 running on x86; Cp1250; en_US (nb) Deadlock appeared when I run tests which create web project. The wizard was frozen at server selection panel. I was not able to reproduce it again or manually. See the end of attached thread dump for affected threads. Found one Java-level deadlock: ============================= "AWT-EventQueue-0": waiting to lock monitor 0x04d3c064 (object 0x213b2e98, a java.lang.Class), which is held by "JavaEEServerModuleFactory" "JavaEEServerModuleFactory": waiting to lock monitor 0x040c3dc4 (object 0x213b2f10, a java.lang.Class), which is held by "AWT-EventQueue-0"