This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 209275 - deadlock creating new JPA project in clean workspace
Summary: deadlock creating new JPA project in clean workspace
Status: VERIFIED FIXED
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: General (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Karen Butzke CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-08 17:19 EST by Karen Butzke CLA
Modified: 2007-11-13 14:44 EST (History)
2 users (show)

See Also:

Attachments
deadlock stack trace (29.03 KB, text/plain)
2007-11-08 17:20 EST, Karen Butzke CLA 		no flags Details
deadlock stack trace (without the dump duplicated) (14.53 KB, text/plain)
2007-11-08 17:25 EST, Karen Butzke CLA 		no flags Details
proposed patch (9.32 KB, patch)
2007-11-12 10:54 EST, Karen Butzke CLA 		no flags Details | Diff
Show Obsolete (1) View All 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 Karen Butzke CLA 2007-11-08 17:19:55 EST 
In a clean workspace choose to create a new JPA Project.
Select the 'Utility JPA project with Java 5.0' configuration and finish the wizard.

The workspace completely locks up.  I will attach the stack trace showing the deadlock.

Using WTP build R3.0/I-I20071108155709-20071108155709
Comment 1 Karen Butzke CLA 2007-11-08 17:20:39 EST 
Created attachment 82498 [details]
deadlock stack trace
Comment 2 Karen Butzke CLA 2007-11-08 17:25:32 EST 
Created attachment 82499 [details]
deadlock stack trace (without the dump duplicated)
Comment 3 David Williams CLA 2007-11-11 17:37:42 EST 
Mind if I change this severity to "critical"? I think deadlocks normally are, since equivalent to a "crash", especially deadlocks on a "main path" of development scenarios. 

Normally I'd say it's a "blocker" except that there is a work around ... just create another simple java project first. 

If you disagree, feel free to change it back ... it is your bug :) ... but, if we do have to go out with M3 with this bug, I want to be sure it's well communicated as one of the huge problems with M3 and I think 'major' just doesn't quite capture it ... considering we have over 200 major bugs :(
Comment 4 Karen Butzke CLA 2007-11-12 10:54:33 EST 
Created attachment 82666 [details]
proposed patch
Comment 5 Karen Butzke CLA 2007-11-12 16:08:10 EST 
Fix has been checked in and released for the M3 build
Comment 6 Neil Hauge CLA 2007-11-13 14:44:36 EST 
Verified in build S-3.0M3-20071112224942.