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.

Bug 205776 - Deadlock when creating web project
Summary: Deadlock when creating web project
Status: NEW
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2011-12-01 13:35 UTC by Jiri Skrivanek
Modified: 2013-08-01 12:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump. (39.10 KB, text/plain)
2011-12-01 13:35 UTC, Jiri Skrivanek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2011-12-01 13:35:27 UTC 
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"
Comment 1 Vince Kraemer 2011-12-05 18:28:34 UTC 
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.
Comment 2 Vince Kraemer 2011-12-05 18:29:15 UTC 
forgot to switch comp/subcomp...
Comment 3 Jiri Rechtacek 2011-12-05 19:12:11 UTC 
No changes in this core during 7.1 cycle, anyway it should be fixed ASAP.