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)" <ji...@apache.org> on 2016/06/15 08:28:09 UTC
[jira] [Created] (QPID-7302) race between auto-delete and
re-declare/consume
Gordon Sim created QPID-7302:
--------------------------------
Summary: race between auto-delete and re-declare/consume
Key: QPID-7302
URL: https://issues.apache.org/jira/browse/QPID-7302
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client
Affects Versions: qpid-cpp-0.34
Reporter: Gordon Sim
Assignee: Gordon Sim
Fix For: qpid-cpp-next
In AMQP 0-10, declare and consume are two distinct operations. When creating a receiver through qpid::messaging, we first declare then consume from the queue.
For a timed auto-delete queue, the delayed auto-delete can tae place between the declare and the consume, resulting in a session error. It would be nice to avoid this. The workaround of course is to set the delay for auto-delete to be sufficiently large that the client will either have reconnected or is likely not reconnecting.
However a simple solution would be to reset the timer on the declare, allowing time for the consume.
This does not prevent the race between a non-timed auto-delete triggered by one session and declare/consume from a different client connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org