[
https://issues.apache.org/jira/browse/QPID-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-633.
-----------------------------
Resolution: Fixed
Revised locking strategy to avoid holding locks (in Queue and SemanticState)
across invocations on other components. This fixes the particular case here
where the queues consumer lock and the semantic states consumer impl lock were
acquired in different orders.
> C++ broker deadlock on subscribe/flow/sync
> ------------------------------------------
>
> Key: QPID-633
> URL: https://issues.apache.org/jira/browse/QPID-633
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Reporter: Rafael H. Schloming
> Assignee: Gordon Sim
> Attachments: flow-stack.txt, subscribe-stack.txt
>
>
> I believe I've encountered a broker deadlock. The client is doing subscribe
> immediately followed by a flow, and then syncing. The client reports sending
> MessageSubscribe, MessageFlow, and ExecutionSync. The broker only reports
> receiving MessageSubscribe and then hangs. I've attached the stack dump from
> the broker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
