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 129700 - Delete MySQL node causes deadlock
Summary: Delete MySQL node causes deadlock
Status: RESOLVED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: David Vancouvering
URL:
Keywords:
Depends on: 130676
Blocks:
  Show dependency tree
 
Reported: 2008-03-10 20:16 UTC by David Vancouvering
Modified: 2008-03-22 06:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
First thread (4.77 KB, text/plain)
2008-03-10 20:19 UTC, David Vancouvering 		Details
Thread 2 (2.62 KB, text/plain)
2008-03-10 20:19 UTC, David Vancouvering 		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 David Vancouvering 2008-03-10 20:16:53 UTC 
The cause is because one thread is calling AdministerAction.enable() using the readAccess() lock on the node hierarchy,
while another thread is trying to remove a node using a writeAccess lock.  The thread doing the enable is trying to see
if the ServerNodeProvider is registered, and this is a synchronized call on ServerNodeProvider.  But the thread that is
trying to remove a node is doing so due to notification from ServerNodeProvider, which is also holding a lock on
ServerNodeProvider (I thought I made sure notify didn't happen inside the synchronization block, but oh well...)
Comment 1 David Vancouvering 2008-03-10 20:19:31 UTC 
Created attachment 58090 [details]
First thread
Comment 2 David Vancouvering 2008-03-10 20:19:48 UTC 
Created attachment 58091 [details]
Thread 2
Comment 3 David Vancouvering 2008-03-22 06:43:42 UTC 
Resolving 130676 should have fixed this, please verify if you can still reproduce this.