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 2009/06/23 13:12:07 UTC
[jira] Resolved: (QPID-1936) Potential for deadlock when using
durable ring queues
[ https://issues.apache.org/jira/browse/QPID-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-1936.
------------------------------
Resolution: Fixed
Fixed by r787625.
> Potential for deadlock when using durable ring queues
> -----------------------------------------------------
>
> Key: QPID-1936
> URL: https://issues.apache.org/jira/browse/QPID-1936
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.5
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Fix For: 0.6
>
>
> When a message is evicted from a durable ring queue (due to arrival of a new message when queue is at its limit), the dequeue request to the store plugin (if loaded) is done with the Queues messageLock held. Depending on the store plugins locking, this causes the potential for deadlocks and shouldbe fixed so that no lock is held when calling dequeue() (as is usually the case).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org