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 37090 - Deadlock between Module-Actions and EQ
Summary: Deadlock between Module-Actions and EQ
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Beans (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2003-11-07 14:43 UTC by pzajac
Modified: 2004-01-21 15:52 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (17.75 KB, text/plain)
2003-11-07 14:43 UTC, pzajac 		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 pzajac 2003-11-07 14:43:11 UTC 
[200310210100]
The deadlock is not reproducible. The
java.awt.Component$AWTTreeLock is locked in
awt-qeue. The Module-Action access to this lock on 
org.openide.awt.Actions$Bridge.propertyChange(Actions.java:274)
.
Comment 1 pzajac 2003-11-07 14:43:55 UTC 
Created attachment 12089 [details]
thread dump
Comment 2 Peter Zavadsky 2003-11-19 14:17:37 UTC 
Not ModuleActions, but somebody from the stack should put the code
into AWT Thread.
I don't know who, passing to first candidate (AddPropertyAction).
Comment 3 Tomas Hurka 2004-01-19 15:08:50 UTC 
Fixed as part of issue #35755.

*** This issue has been marked as a duplicate of 35755 ***
Comment 4 Jesse Glick 2004-01-19 16:14:47 UTC 
I doubt it. Issue #35755 did not change the default behavior of any
actions except those listed; you have to override asynchronous() to
return false to make it take effect. beans.AddPropertyAction does not
yet do this from what I can see.

Anyway #35755 was fixed well before this issue was even opened.
Comment 5 Tomas Hurka 2004-01-20 16:52:46 UTC 
OK, Jesse you are right. It was fixed in ElementNode.ElementListener.propertyChange(), 
which runs in event thread.
Comment 6 pzajac 2004-01-21 15:52:12 UTC 
it looks fine