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 21867 - IDE went into deadlock state and restarting the IDE did not help to come out of that state
Summary: IDE went into deadlock state and restarting the IDE did not help to come ou...
Status: CLOSED DUPLICATE of bug 19635
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: Sun Solaris
: P1 blocker (vote)
Assignee: David Simonek
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2002-03-26 01:15 UTC by Srinivas Gundeaboina
Modified: 2008-12-23 10:49 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump of ide when it was in deadlock state (28.50 KB, text/plain)
2002-03-26 01:18 UTC, Srinivas Gundeaboina 		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 Srinivas Gundeaboina 2002-03-26 01:15:50 UTC 
I was creating CMP beans when this happened.  I was adding a finder method with
an invalid column name in the where clause of EJB QL.  I was getting some
exceptions.
To reproduce the problem, I deleted the bean and using the same package tried to
create a j2ee->CMP bean.  The IDE went into a deadlock state.

I restarted the IDE,  tried to create the CMP Bean, it went into deadlock state
again.

I am attaching the thread dump.
Comment 1 Srinivas Gundeaboina 2002-03-26 01:18:50 UTC 
Created attachment 5177 [details]
thread dump of  ide when it was in deadlock state
Comment 2 _ ttran 2002-03-26 09:15:48 UTC 
we will investigate, but first of all please upgrade your JDK.  I see
that you are using jdk 1.4.0 rc.  1.4.0 FCS has been released for
quite some time
Comment 3 David Simonek 2002-03-26 09:51:27 UTC 
Duplicate of 19635, already fixed in netbeans code. Although stack
traces attached to 19635 are not exactly the same, reason is identical
- DefaultContainerImpl and SplitContainerImpl wrongly synchronized on
the same lock.

*** This issue has been marked as a duplicate of 19635 ***
Comment 4 Quality Engineering 2003-07-01 15:48:54 UTC 
Resolved for 3.4.x or earlier, no new info since then -> verified.
Comment 5 Quality Engineering 2003-07-01 16:20:04 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.