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 16600 - Stop using Folder Children thread for refreshing content of folders
Summary: Stop using Folder Children thread for refreshing content of folders
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Data Systems (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: David Strupl
URL:
Keywords: THREAD
Depends on: 16432
Blocks:
  Show dependency tree
 
Reported: 2001-10-16 10:33 UTC by Jaroslav Tulach
Modified: 2008-12-22 17:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jaroslav Tulach 2001-10-16 10:33:55 UTC 
There has been a deadlock trouble in FolderChildren that resulted in creating
new request processor for calling setKeys (....) on children. The trouble was
that setKeys often blocked waiting to get write mutex access and the mutex was
hold by another thread waing for FolderChildren.findChild (...) method to
finish.
Comment 1 Jaroslav Tulach 2001-10-16 10:35:11 UTC 
It is not possible to solve this issue right now, but after the
enhancement described in issue #16432 will be implemented, please use
those methods and get rid of the FolderChildren thread.
Comment 2 Jesse Glick 2002-05-31 15:08:50 UTC 
Note that without explicit help from #16432, you can use
RequestProcessor.getDefault().post(...) to post something which then
does Mutex.writeAccess. See ModuleBean for examples.
Comment 3 Marek Grummich 2002-07-22 11:22:42 UTC 
Set target milestone to TBD
Comment 4 Marek Grummich 2002-07-22 11:24:50 UTC 
Set target milestone to TBD
Comment 5 David Strupl 2003-02-23 23:01:38 UTC 
Jarda, does this still apply? After recent changes in 
FolderChildren?
Comment 6 Jaroslav Tulach 2003-02-24 09:53:07 UTC 
I think this is fixed now.
Comment 7 pzajac 2003-07-31 10:53:54 UTC 
The deadlock didn't occured long time.