You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2008/10/30 12:19:44 UTC

[jira] Updated: (QPID-684) Use non-recursive mutexes for c++ qpid::sys::Mutex

     [ https://issues.apache.org/jira/browse/QPID-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gordon Sim updated QPID-684:
----------------------------

        Fix Version/s:     (was: M4)
    Affects Version/s: M3

> Use non-recursive mutexes for c++ qpid::sys::Mutex
> --------------------------------------------------
>
>                 Key: QPID-684
>                 URL: https://issues.apache.org/jira/browse/QPID-684
>             Project: Qpid
>          Issue Type: Improvement
>          Components: C++ Broker, C++ Client
>    Affects Versions: M3
>            Reporter: Alan Conway
>            Priority: Minor
>
> Switch qpid::sys::Mutex to use non-recursive mutexes and fix any deadlocks that result.
> We should never be locking recursively and we want to get an obvious error/deadlock if we do so we can fix the problem.
> Recursive mutexes are a Bad Thing, google for the apology by the guy who invented them if you want to know more. He  never intended them to be used for anything other than as a gross hack for when you had to make thread-unsafe libraries thread safe but didn't have time to design it properly.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.