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 37532 - Startup deadlock
Summary: Startup deadlock
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Marian Petras
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2003-11-26 14:45 UTC by _ pkuzel
Modified: 2004-06-16 13:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
The deadlock (15.65 KB, text/plain)
2003-11-26 14:46 UTC, _ pkuzel 		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 _ pkuzel 2003-11-26 14:45:08 UTC 
thread dump attached
Comment 1 _ pkuzel 2003-11-26 14:46:51 UTC 
Created attachment 12321 [details]
The deadlock
Comment 2 Jiri Rechtacek 2003-11-26 15:11:51 UTC 
Datasystem's owner, it could be on your side. Pls, look an it.
Comment 3 David Konecny 2003-11-27 09:16:59 UTC 
Yarda, your knowledge is needed here. Could you please look at the
thread dump and say what is wrong?

pkuzel, how often it happens?
Comment 4 _ pkuzel 2003-11-27 09:24:44 UTC 
It happens whenever JUnit action creation (via layer) in Folder
Instance Processor thread crosses its locking with AWT.
Comment 5 Jaroslav Tulach 2003-11-27 11:47:24 UTC 
I suggest fix in:
org.netbeans.modules.junit.CreateTestAction.<init>(CreateTestAction.java:163)
to not create the JPanel (subclass).

Btw. actions should construct their data in
SharedClassObject.initialize not in constructor.
Comment 6 David Konecny 2003-11-27 12:55:26 UTC 
Thanx Yarda. Passing to JUnit.
Comment 7 Marian Petras 2003-12-01 13:23:43 UTC 
Jaroslav Tulach is right - the JPanel should not be created during
startup. I will fix it.
Comment 8 Marian Petras 2003-12-02 07:38:54 UTC 
Fixed in the trunk.

The JPanel is no more created during instance initialization.
Comment 9 dmladek 2004-06-16 13:39:27 UTC 
no more deadlock in current dev build