Bug 387342 - Deadlock in ConcurrencyManager
Summary: Deadlock in ConcurrencyManager
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P2 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2012-08-16 01:09 EDT by Craig Day CLA
Modified: 2022-06-09 10:10 EDT (History)
2 users (show)

See Also:

Attachments
thread dump (90.97 KB, text/plain)
2012-08-16 01:09 EDT, Craig Day CLA 		no flags Details
Image of CocurrencyManager state (105.31 KB, image/png)
2012-08-16 01:10 EDT, Craig Day 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 Craig Day CLA 2012-08-16 01:09:43 EDT 
Created attachment 219941 [details]
thread dump

We have somehow deadlocked the concurrency manager in 2.3.2. ConcurrencyManager shows numberOfReaders = 1, activeThread = null... full state in attached image. Thread dump also attached.
Comment 1 Craig Day CLA 2012-08-16 01:10:31 EDT 
Created attachment 219942 [details]
Image of CocurrencyManager state
Comment 2 Gordon Yorke CLA 2012-09-26 13:32:14 EDT 
Unfortunately the thread dump shows all of the active threads waiting with the same stack. This leave no indication of what actually happened and how the ConcurrencyManager got into this state.

Is this occurring regularly and is it reproducible?
Is this the full stack trace without anything removed?
Are there any errors or exceptions in the log? 
What kind of load was the system experiencing when the issue occurred?
Comment 3 Gordon Yorke CLA 2012-10-02 09:29:15 EDT 
Marked as resolved until further information is provided from bug filer.
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:10:48 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink