You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rafael H. Schloming (JIRA)" <qp...@incubator.apache.org> on 2007/10/10 19:52:50 UTC
[jira] Updated: (QPID-633) C++ broker deadlock on
subscribe/flow/sync
[ https://issues.apache.org/jira/browse/QPID-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming updated QPID-633:
-------------------------------------
Attachment: subscribe-stack.txt
> 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
> Attachments: 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.