Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346891 - Regression: Deadlock closing a JPA project with a diagram editor open
Summary: Regression: Deadlock closing a JPA project with a diagram editor open
Status: CLOSED DUPLICATE of bug 339900
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: Diagram Editor (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: 3.0 RC3   Edit
Assignee: Project Inbox CLA
QA Contact: Stefan Dimov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-23 12:30 EDT by Neil Hauge CLA
Modified: 2011-05-25 11:33 EDT (History)
1 user (show)

See Also:

Attachments
Thread dump (22.33 KB, text/plain)
2011-05-23 12:30 EDT, Neil Hauge 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 Neil Hauge CLA 2011-05-23 12:30:58 EDT 
Created attachment 196360 [details]
Thread dump

This appears to be a regression in RC2 caused by the fix for bug 346728 but I have not confirmed this.

To reproduce:

-Create a new JPA project
-Generate a few entities from DB or code some up by hand
-Open the diagram editor
-Add a few of the already created entities to the diagram editor
-Save the diagram
-Close the JPA project

The close project action does not succeed as a deadlock occurs.  Thread dump is attached.

It appears that the diagram editor is trying to force a save of one of the entities during the project close job, which doesn't seem like a good thing, especially since everything in the project is in a saved state already.  Also, nothing should be committed during project close without getting confirmation from the user.  Not sure if this is related to the deadlock, but thought I would mention it.
Comment 1 Neil Hauge CLA 2011-05-23 18:37:44 EDT 
Lowering severity to major since you can escape the deadlock with the Jobs UI dialog.  This may be related to bug 339900, or at least it has similarities, although in this case, the editor is in a saved state, unlike in bug 339900 where the editor is dirty.
Comment 2 Neil Hauge CLA 2011-05-25 11:33:16 EDT 

*** This bug has been marked as a duplicate of bug 339900 ***