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 166073 - Deadlock when importing V3 servers.
Summary: Deadlock when importing V3 servers.
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-27 04:01 UTC by _ pcw
Modified: 2009-05-28 08:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (46.95 KB, text/plain)
2009-05-27 04:02 UTC, _ pcw 		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 _ pcw 2009-05-27 04:01:23 UTC 
Start 6.5 with a clean userdir.
Add V3 prelude and shutdown.
Start 6.7 with a clean userdir and when it asks about importing from 6.5, say YES.
Close Start Page
Switch to Services Page.
Open Servers Node.
You'll see an "Activating JavaEE Modules..." dialog appear and after a short time, it will freeze.
-> Deadlock.

Thread dump attached.
Comment 1 _ pcw 2009-05-27 04:02:02 UTC 
Created attachment 82832 [details]
thread dump
Comment 2 _ pcw 2009-05-27 04:06:50 UTC 
Caused by simultaneous initialization of V3 server instance provider from each end -- one side coming in from common
server (AsyncChildren...) and the other from j2eeserver module via the j2eeserver-common server bridge.

Fix unclear at this point in time.
Comment 3 Vince Kraemer 2009-05-27 04:16:39 UTC 
actually.. this is with the trunk... not the release67 clone...
Comment 4 _ pcw 2009-05-27 05:22:35 UTC 
So not reproducible with clone right now?  Is that with or without pending fixes from trunk?
Comment 5 Vince Kraemer 2009-05-27 05:32:25 UTC 
I think the 'fix' for issue 166017 introduced the deadlock... but that issue is also P1...

So, I am still trying to find a reasonable fix for 166017, that avoids triggering this deadlock.
Comment 6 _ pcw 2009-05-27 05:42:54 UTC 
Got it.  I agree, that introduced the deadlock.  I didn't realize that change wasn't in the release clone.
Comment 7 Vince Kraemer 2009-05-27 06:10:41 UTC 
corrected the version info...
Comment 8 Vince Kraemer 2009-05-27 14:03:47 UTC 
reverted....

http://hg.netbeans.org/web-main/rev/6e7c79f082f0
Comment 9 Quality Engineering 2009-05-28 08:44:07 UTC 
Integrated into 'main-golden', will be available in build *200905280201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/6e7c79f082f0
User: vince kraemer <vkraemer@netbeans.org>
Log: #166073: bad fix for 66017... triggers a deadlock