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 14263 - Deadlock due too early initialization of settings
Summary: Deadlock due too early initialization of settings
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-08 13:16 UTC by Jaroslav Tulach
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump (10.64 KB, text/plain)
2001-08-08 13:18 UTC, Jaroslav Tulach 		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 Jaroslav Tulach 2001-08-08 13:16:37 UTC 
I am attaching a deadlock which I believe is caused by ElementNode initializing
settings as static field. Could this be delayed?
Comment 1 Jaroslav Tulach 2001-08-08 13:18:48 UTC 
Created attachment 2097 [details]
Thread dump
Comment 2 Tomas Hurka 2001-08-09 09:21:57 UTC 
I will look at it.
Comment 3 Jaroslav Tulach 2001-08-09 10:31:29 UTC 
I have modified LoaderPoolNode to call Section.getInstance without
holding any locks so the deadlock should disapper. Still Tomas, try to
initialize the settings lazily.
Comment 4 Tomas Hurka 2001-08-09 18:13:55 UTC 
Unfortunately lazy initialization is not possible without API changes.
The modification of LoaderPoolNode is sufficient to prevent reported
deadlock. I am setting resolution to FIXED.
Comment 5 Quality Engineering 2003-07-01 15:54:06 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified
Comment 6 Quality Engineering 2003-07-01 16:14:29 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.
Comment 7 Quality Engineering 2007-09-20 09:50:31 UTC 
Reorganization of java component