Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 346891

Summary:

Regression: Deadlock closing a JPA project with a diagram editor open

Product:

[WebTools] Dali JPA Tools

Reporter:

Neil Hauge <neil.hauge>

Component:

Diagram Editor

Assignee:

Project Inbox <dali.diagrameditor-inbox>

Status:

CLOSED DUPLICATE

QA Contact:

Stefan Dimov <stefan.dimov>

Severity:

major

Priority:

CC:

brian.vosburgh

Version:

3.0

Target Milestone:

3.0 RC3

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
Thread dump	none

Description Neil Hauge

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

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

2011-05-25 11:33:16 EDT


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