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 16372 - Deadlock when trying to create new 'Java Package'
Summary: Deadlock when trying to create new 'Java Package'
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: corba (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-09 12:45 UTC by vnemec
Modified: 2003-06-30 17:07 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (8.38 KB, text/plain)
2001-10-09 12:46 UTC, vnemec 		Details
Full thread dump of the next deadlock. (20.78 KB, text/plain)
2001-10-09 12:54 UTC, Jan Lahoda 		Details
'Xdebug' thread dump (9.62 KB, text/plain)
2001-10-09 14:51 UTC, vnemec 		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 vnemec 2001-10-09 12:45:42 UTC 
[Orion 011008_1, jdk1.3.1, redhat7.1]
see attached thread dump
Comment 1 vnemec 2001-10-09 12:46:41 UTC 
Created attachment 2920 [details]
stack trace
Comment 2 Jan Lahoda 2001-10-09 12:52:58 UTC 
It happened me on Orion 011008_1, Solaris. In the thread dump I got is
not corba at all, so I consider this general bug and moving it to
openide. I am attaching my thread dump.
Comment 3 Jan Lahoda 2001-10-09 12:54:04 UTC 
Created attachment 2921 [details]
Full thread dump of the next deadlock.
Comment 4 Svata Dedic 2001-10-09 13:38:51 UTC 
Yarda said:
IDLObject and JavaDataObject are the bad guys -- they call files() [or
secondaryEntries() during their constructor execution, which is the
same in effect]. This will trigger (nested) recognition of the same
DataObject.
Comment 5 vnemec 2001-10-09 14:46:06 UTC 
Corba has been recognized as a 'bad guy' => reassigning back to corba
and attaching 'Xdebug' thread dump
Comment 6 vnemec 2001-10-09 14:51:24 UTC 
Created attachment 2924 [details]
'Xdebug' thread dump
Comment 7 Tomas Zezula 2001-10-09 15:15:47 UTC 
Fine, IDLDataObject wil not call secondaryEntries in its constructor.
Comment 8 Jaroslav Tulach 2001-10-09 15:32:27 UTC 
I've done an improvement to solve Jan Lahoda's stack trace, but that
is not the problem. The real problem is in corba.

Few comments to the IDLDataObject code:

1. Line 1213 waits for being notified but I was not able to find out
who should notify the data object!? Is this some kind of good
programing practice to have wait and notify in different source files?

2. Please do not call update in constructor for performance reasons,
if you need override files () method...
Comment 9 _ ttran 2001-10-09 15:36:24 UTC 
whenever you change the component field, please always remember to
reset the "Assign To" and "QA Contact" field
Comment 10 Jan Lahoda 2001-10-09 15:49:34 UTC 
So, I tried to reproduce this problem with corba module disabled, and
I was not able to reproduce the problem.
Comment 11 Tomas Zezula 2001-10-09 16:35:28 UTC 
I am not autohor of this code, but I think that the wait on line 1213
is notified from line 1094. On the line 1213 is waiting on the
IDLParser output which is needed to find out possible file names which
 the IDLDataObject should hide.
The update was removed from constructor. The costructor only schedules
the job in RequestProcessor, the Task is responsible for parsing the
IDL, the parse is need to determine the java FileObject names, which
are derived from names of IDL elements.
Comment 12 David Kaspar 2001-10-10 11:12:00 UTC 
Verified
Comment 13 Quality Engineering 2003-06-30 17:07:10 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.