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 16194 - Deadlock on startup, when have directories open that have AppAsm objects & Web directories
Summary: Deadlock on startup, when have directories open that have AppAsm objects & We...
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P3 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2001-10-03 19:41 UTC by Roger Blumer
Modified: 2008-12-22 21:32 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump for deadlock (13.74 KB, text/plain)
2001-10-03 19:44 UTC, Roger Blumer 		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 Roger Blumer 2001-10-03 19:41:41 UTC 
I got a deadlock when trying to start up Orion.  After killing it, the next start finished successfully.

The attached trace has activity in the Folder Recognizer task & the OpenIDE task, processing AppAsm objects & Web objects, plus activity 
on the AWT-EventQueue task processing layers.  The userdir I was using had one Web directory mounted, plus two directories open that 
contained several AppAsm objects & EJB objects in them.

The build I was using was updated at 27 Sep 2001 17:00:14 GMT.
It included the FolderOrder change from bug 15918.
This problem may also be related to bug 15378.
Comment 1 Roger Blumer 2001-10-03 19:44:56 UTC 
Created attachment 2833 [details]
Thread dump for deadlock
Comment 2 Jan Zajicek 2001-10-04 09:43:35 UTC 
Why assigned to setting? I do not see any deadlock in the thread dump.
Can someone help to investigate this, Petr or Jesse? Thanks.
Comment 3 Jesse Glick 2001-10-07 19:31:56 UTC 
This looks like a *possible* duplicate of issue #15378 though the
openide req processor is not waiting on a monitor as was typical for
that bug. Roger I assume you could not reproduce this?
Comment 4 Roger Blumer 2001-10-08 18:13:12 UTC 
No, I haven't been able to reproduce this.
It only happened the one time.
The reason I added it as a different bug than 15378 is that this was a 
deadlock with no CPU activity, while 15378 was constant CPU activity 
(at least on my machine).  Plus the IDE never fully came up (even 
after 15 minutes or so).
But the bugs certainly could be related.
Comment 5 Jesse Glick 2001-10-08 19:12:18 UTC 
If there was no CPU activity then it is probably not a dupe of #15378,
rather some garden-variety deadlock.
Comment 6 Jan Chalupa 2001-11-27 13:03:20 UTC 
Target milestone -> 3.3.1.
Comment 7 Petr Nejedly 2002-04-16 12:29:29 UTC 
Was fixed long time ago in ProxyClassLoader v1.6:
revision 1.6
date: 2001/10/08 14:37:21;  author: pnejedly;  state: Exp;  lines: +13
-0
branches:  1.6.26;
Fixes deadlock with one thread loading a class from known package and
the second
 loading a class from new package - there was wrong locking order so
I'm adding 
proper synchronization
Comment 8 Jan Zajicek 2002-04-18 14:20:53 UTC 
verified
Comment 9 Quality Engineering 2003-07-01 16:36:10 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.