Can you show the MonitorMixin complete error? Im finding it interesting that its still deadlocking with MM in place. Not sure I have a solution, but before I broach it, Id like to see the full trace if possible. -- D. Deryl Downey "The bug which you would fright me with I seek" - William Shakespeare - The Winter's Tale, Act III, Scene II - A court of Justice. *From:* Abhijit Sarkar <email@example.com> *Sent:* February 14, 2013 10:09 PM *To:* ruby-talk ML <firstname.lastname@example.org> *Subject:* Re: Ruby Multithreaded producer-consumer problem I rewrote the code using MonitorMixin and then back to using Mutex, same result. I used 2 ConditionVariable, same result :( If it's not working, it's certainly not for the lack of trying. Attachments: http://www.ruby-forum.com/attachment/8132/orange_tree.rb
on 2013-02-15 15:50
on 2013-02-15 22:51
D. Deryl Downey wrote in post #1097093: > Can you show the MonitorMixin complete error? I posted it in my original post. I am not sure of the difference between the mailing list and online forum but it's creating a helluva confusion for me.
on 2013-02-24 13:16
On Fri, Feb 15, 2013 at 3:44 PM, D. Deryl Downey <email@example.com> wrote: > Can you show the MonitorMixin complete error? Im finding it interesting > that its still deadlocking with MM in place. MM vs. Monitor only helps with reentrancy. Deadlocks are usually an issue which can be solved by imposing a fixed order of lock acquisition. Kind regards robert