[GROOVY-1890] MemoryAwareConcurrentReadMap cause thred dead lock,it will hang our application at some time.

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.1-beta-1
• Fix Version/s: 1.1-beta-2
• Component/s: groovy-jdk
• Environment: Windows Xp /jdk1.5
• Flags: Patch
• Assignee: Jochen Theodorou
• Reporter: Dongyong Wang
• Created: 12/May/07 16:18
• Updated: 05/Apr/15 14:25
• Resolved: 16/May/07 15:03

Description

The class org.codehaus.groovy.runtime.metaclass.MemoryAwareConcurrentReadMap deal with the realization of the visit with multithreading is not doing well enough, often lead to deadlock. The worst result is that an application will hang because of it.

The problem is the writeLock and writeQueue. I don't think the writeQueue is must be used in the code,and It somewhat redundant.
It's possible to implement the same function without writeQueue.

May be I'm wrong about wrietQueue,but the bug is true and is very Serious .

I can not imagine, if the bug is real, use grail to realize a project. What we will get?

The test case will show the "dead lock" when you run it some times.
I wish the patch should be helpful also.

Thanks.

Issue Links

• is duplicated by: GROOVY-1964 deadlock in MemoryAwareConcurrentReadMap.get