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 19364

Summary:	Deadlock involving DataObject.dispose + node
Product:	platform	Reporter:	Jesse Glick <jglick>
Component:	Data Systems	Assignee:	David Strupl <dstrupl>
Status:	CLOSED DUPLICATE
Severity:	blocker	Keywords:	THREAD
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	Linux
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Thread dump Thread dump

Description Jesse Glick 2002-01-11 18:01:05 UTC

[r33 jan 10] While reinstalling apisupport, as usual: the deadlock
generator :-) I'm not sure that what apisupport is doing in its reload
thread is completely fine, but one apparent problem in the request
processor is that DataObject.dispose (presumably holding whatever
datasystems-specific locks etc.) winds up causing DataNode to
fireNodeDestroyed, which can enter the node mutex. This looks to me
like an incorrect lock ordering: creating a DataObject (which resulted
in the call to dispose()) ought not try to get the node mutex.

Suggest that DataNode react to DataObject property changes asynch.

Comment 1 Jesse Glick 2002-01-11 18:02:38 UTC

Created attachment 4121 [details]
Thread dump

Comment 2 Jesse Glick 2002-01-19 14:58:31 UTC

Again in [dev jan 19] while reinstalling apisupport.

Comment 3 Jesse Glick 2002-01-19 14:58:57 UTC

Created attachment 4294 [details]
Thread dump

Comment 4 David Strupl 2002-07-01 13:26:56 UTC

This is the same as #21107. Was fixed by phamernik.

*** This issue has been marked as a duplicate of 21107 ***

Comment 5 Quality Engineering 2003-07-01 15:53:50 UTC

Resolved for 3.4.x or earlier, no new info since then -> verified

Comment 6 Quality Engineering 2003-07-01 16:15:24 UTC

Resolved for 3.4.x or earlier, no new info since then -> closing.