Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359035 - Deleting a locked object leaves dangling locks in the LockManager
Summary: Deleting a locked object leaves dangling locks in the LockManager
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 4.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Caspar D. CLA
QA Contact: Eike Stepper CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 06:06 EDT by Caspar D. CLA
Modified: 2012-09-21 07:18 EDT (History)
1 user (show)

See Also:
stepper: review+

Attachments
Testcase (as Java snippet) (1.14 KB, text/plain)
2011-09-27 06:08 EDT, Caspar D. CLA 		no flags Details
Patch v1 (Git patch) (8.62 KB, patch)
2011-11-09 02:03 EST, Caspar D. 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 Caspar D. CLA 2011-09-27 06:06:45 EDT 
When a client deletes an object while holding one or more locks
on it, those locks are not removed from the lockManager's internal
map. They remain as dangling locks.
Comment 1 Caspar D. CLA 2011-09-27 06:08:53 EDT 
Created attachment 204064 [details]
Testcase (as Java snippet)
Comment 2 Caspar D. CLA 2011-11-09 02:03:14 EST 
Created attachment 206648 [details]
Patch v1 (Git patch)

Please apply patch with 'git apply /path/to/the/patch.txt'
Comment 3 Eike Stepper CLA 2012-01-31 00:32:00 EST 
commit 4325b01b3e4e9c8f97d64e8756029c44ad424776
Comment 4 Eike Stepper CLA 2012-09-21 07:18:14 EDT 
Closing.