Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 326966 - Log when DeadlockDetector resolves a deadlock
Summary: Log when DeadlockDetector resolves a deadlock
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.7 M3   Edit
Assignee: John Arthorne CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-04 15:29 EDT by John Arthorne CLA
Modified: 2011-07-18 04:07 EDT (History)
2 users (show)

See Also:


Attachments
Fix (1.47 KB, patch)
2010-10-06 14:14 EDT, John Arthorne CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2010-10-04 15:29:37 EDT
When DeadlockDetector resolves a deadlock, it doesn't log anything by default. This can obscure errors in client code, or even bugs in the deadlock detection code itself (such as bug 262032). We should consider enabling it by default.
Comment 1 James Blackburn CLA 2010-10-04 15:37:45 EDT
This is a very good idea! I wasn't even aware that deadlocks were resolved silently until I dug deeper.
Comment 2 John Arthorne CLA 2010-10-06 14:14:20 EDT
Created attachment 180362 [details]
Fix
Comment 3 John Arthorne CLA 2010-10-06 14:14:46 EDT
Fix released.