Keeping UI tread alive causes Deadlocks

[pcdavid]

• 🆔 Bugzilla ID: #308806
• 📘 Project: Modeling / EMF Services / Transaction
• 🗓 Created: 2010-04-12T09:07:53Z
• ❓ Status: NEW /

[pcdavid]

Comment #0 on Mon Apr 12 2010 11:07:53 GMT+0200 (Central European Summer Time):

Build Identifier: M20090917-0800

Hi,

we are using GEF, EMF and EMF Transaction to realize a visual modeling tool. Sometimes we have deadlocks whose thread dumps leads me to the suspicion that they will be caused by the order in which the transaction framework tries to assign the active transaction to a thread an the UI thread keep alive strategy.

See attached file for newsgroup discussion with Christian.

Here an exemplary thread dump. Note, there is no other thread with an active transaction.

Thread [main] (Suspended)
  (WorkManager locked)
  WorkManager.checkIn()
  JavaModelManager.initializeAllContainers()
  Display.readAndDispatch()
  (need transaction -> not acquired)
  Viewer.refresh()
  Main.main(String[])

Thread [Worker-3] (Suspended)
  (need transaction)
  ourResourceListener.resourceChanged()
  NotificationManager.notify()
  (WorkManager locked)
  Workspace.endOperation()
  Worker.run()

Currently I have no proposal for a solution. In my opinion it is a good and necessary idea to keep the UI thread alive.

Reproducible: Always

---

Comment #1 on Mon Apr 12 2010 11:12:01 GMT+0200 (Central European Summer Time):

---

Comment #2 on Tue May 03 2011 19:06:00 GMT+0200 (Central European Summer Time):

See also bug 249951, if we didn't hold the workspace lock during the notification it looks like this deadlock would go away.

---

Comment #3 on Sat May 14 2022 15:51:27 GMT+0200 (Central European Summer Time):

Eclipse EMF Transaction is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/emf-transaction.

If this issue is relevant to you and still present in the latest release:

* Create a new issue at https://github.com/eclipse/emf-transaction/issues/.
  * Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  * In the GitHub description, start with a link to this bugzilla ticket
  * Optionally add new content to the description if it can helps towards resolution
* Update bugzilla ticket
  * Add to "See also" property (up right column) the link to the newly created GitHub issue
  * Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  * Set status as CLOSED MOVED

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for EMF Transaction will be archived and made read-only.