Bug 981638 - support standard lifetime policies for AMQP 1.0
Summary: support standard lifetime policies for AMQP 1.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: Development
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: 3.0
: ---
Assignee: Gordon Sim
QA Contact: Petr Matousek
URL:
Whiteboard:
Depends On:
Blocks: 1010399
TreeView+ depends on / blocked
 
Reported: 2013-07-05 11:05 UTC by Gordon Sim
Modified: 2015-01-21 12:54 UTC (History)
5 users (show)

Fixed In Version: qpid-qmf-0.22-7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-21 12:54:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-4976 0 None None None Never
Apache JIRA QPID-5463 0 None None None Never
Red Hat Bugzilla 1051441 0 high CLOSED Broker segfault when wrong filter used 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1051453 0 medium CLOSED [amqp1.0] delete-if-unused lifetime policy not applied after the sender's link is closed 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1059784 0 low NEW [amqp1.0] delete-on-close policy do not work for exchanges 2021-02-22 00:41:40 UTC

Internal Links: 1051441 1051453 1059784

Description Gordon Sim 2013-07-05 11:05:29 UTC 
Description of problem:

The AMQP specification defines lifetime policies that can be select for dynamically created nodes: delete-on-close, delete-on-no-links, delete-on-no-messages, delete-on-no-links-or-messages.

Allowing these to be specified through the qpid::messaging API, and having qpidd recognise and implement them is desirable.
Comment 1 Gordon Sim 2013-07-10 14:03:02 UTC 
Fixed upstream: https://svn.apache.org/r1501768
Comment 6 Petr Matousek 2014-02-04 13:47:48 UTC 
The amqp1.0 defined standard lifetime policies for dynamic nodes are implemented and works as expected.

packages under test:
qpid-cpp-*-0.22-33

-> VERIFIED
Note You need to log in before you can comment on or make changes to this bug.