Bug 128399 - Deadlock while checking consistency of type info history
Summary: Deadlock while checking consistency of type info history
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P2 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: Dirk Baeumer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-17 08:35 EST by Tobias Widmer CLA
Modified: 2006-03-28 06:06 EST (History)
0 users

See Also:

Attachments
thread dump (19.05 KB, text/plain)
2006-02-17 08:40 EST, Tobias Widmer CLA 		no flags Details
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 Tobias Widmer CLA 2006-02-17 08:35:03 EST 
3.2 M4

This is maybe related to bug 123224

Attaching thread dump...
Comment 1 Tobias Widmer CLA 2006-02-17 08:40:04 EST 
Created attachment 34911 [details]
thread dump
Comment 2 Dirk Baeumer CLA 2006-02-17 09:04:10 EST 
Not a dup of 123224.

The problem is that the update job could initialize the Java model hence requesting a Java model lock. So the update job must specify a scheduling rule.

The deadlock occurs since the PDE feature builder builds a project resulting in a delta notification which marks the type history as inconsistent.
Comment 3 Dirk Baeumer CLA 2006-02-20 05:35:26 EST 
Fixed.
Comment 4 Tobias Widmer CLA 2006-03-28 06:06:26 EST 
Verified using I20060328-0010