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 20668 - Deadlock in xtest - org.openide.loaders.DataFolderTest
Summary: Deadlock in xtest - org.openide.loaders.DataFolderTest
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Lookup (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: phamernik
URL:
Keywords: RANDOM, THREAD
: 20747 (view as bug list)
Depends on: 20549
Blocks:
  Show dependency tree
 
Reported: 2002-02-19 14:22 UTC by Milan Kubec
Modified: 2008-12-22 22:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
full thread dump (15.11 KB, text/plain)
2002-02-19 14:24 UTC, Milan Kubec 		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 Milan Kubec 2002-02-19 14:22:52 UTC 
There is deadlock in test org.openide.loaders.DataFolderTest when running under
continuous xtest framework. Thread dump is attached.
Comment 1 Milan Kubec 2002-02-19 14:24:28 UTC 
Created attachment 4745 [details]
full thread dump
Comment 2 David Strupl 2002-02-20 13:44:48 UTC 
DataObjectPool's static initializer calls TopManager.getDefault().
This call waits for FolderInstance to finish. But "Folder recognizer"
thread also wants to access the DataObjectPool class.
Comment 3 David Strupl 2002-02-25 14:05:29 UTC 
Milan, are you able to reproduce the bug? We would need to verify that
the solution helps.
Comment 4 David Strupl 2002-02-25 14:37:52 UTC 
This bug can be fixed easily with enhancement 20549 implemented.
ErrorManager could call non blocking variant of allInstances to
prevent this deadlock.
Comment 5 phamernik 2002-03-08 12:49:43 UTC 
*** Issue 20747 has been marked as a duplicate of this issue. ***
Comment 6 phamernik 2002-03-08 15:06:37 UTC 
Fixed in 8 files of org.openide.loaders.* package.

Static field DataObjectPool.POOL was changed to private and new access
method was created ( getPOOL() ). The POOL shouldn't be accessed
directly, but only using this method.
Comment 7 pzajac 2002-10-11 16:12:59 UTC 
verified, it seems be ok.
Comment 8 Quality Engineering 2003-07-01 16:13:36 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.