[Ace-users] [ace-bugs] trying to fix an ACE hang

[Greg Popovitch]

Hi guys,

Just wanted to let you guys know that changing the priority of my
dequeuing thread didn't help with my deadlock issue. 

However moving the "this->notify()" out of the Message_Queue's guard
scope did the trick, with no obvious ill effects, so I'll try living
with this change for a while.

I think this is a serious problem and I do agree it deserves a bugzilla
entry and a comment in the code... and probably some immediate attention
from the ACE developers :-)

greg

-----Original Message-----
From: Douglas C. Schmidt [mailto:schmidt at dre.vanderbilt.edu] 
Sent: Friday, November 30, 2007 12:22 PM
To: Greg Popovitch; ace-bugs at cse.wustl.edu
Subject: Re: [ace-bugs] trying to fix an ACE hang

Hi Folks,

   It would be a good idea to capture this discussion in a bugzilla
entry so we don't lose track of the details?  It would also be a good
idea to add a comment in the ACE code that refers to this entry so we
don't need to re-discover this each time someone asks.

Thanks,

        Doug

><This may help. Also, I don't recall a description of your dequeueing
>thread(s), but if it could avoid the need to be notified on new queue
>content, this problem would go away for you.>
>
>Thanks, Steve, but I don't think I can do this. This dequeuing
thread=20
>also waits for read events on a socket. It serves as an intermediate=20
>to communicate with a server process, where all the i/o is done in
the=20
>low priority thread.
>
>I do appreciate the help and suggestions. I do hope that this issue in
>ACE will be addressed by the ACE team - it seems quite serious to
me.=20
>
>Thanks,
>
>greg
>
>
>

-- 
Dr. Douglas C. Schmidt                       Professor and Associate
Chair
Electrical Engineering and Computer Science  TEL: (615) 343-8197
Vanderbilt University                        WEB:
www.dre.vanderbilt.edu/~schmidt
Nashville, TN 37203                          NET:
d.schmidt at vanderbilt.edu