Keith Wall created QPID-7625:
--------------------------------
Summary: AMQP 1.0 temporary queues are not deleted in response to
JMS TemporaryQueue#delete
Key: QPID-7625
URL: https://issues.apache.org/jira/browse/QPID-7625
Project: Qpid
Issue Type: Bug
Reporter: Keith Wall
Fix For: qpid-java-7.0
As shown by system test
{{TemporaryQueueTest#testExplictTemporaryQueueDeletion}}. When the application
calls {{TemporaryQueue#delete()}} the temporary queue ought to be deleted
immediately. This currently does not happen.
The following describes how sending links with certain properties are used to
establish temporary queues.
https://www.oasis-open.org/committees/download.php/56418/amqp-bindmap-jms-v1.0-wd06.pdf
The Qpid JMS Client correctly sends the detach in response to the {{#delete}}
call, but it appears that the broker's AMQP 1.0 protocol layer does not
organise itself to act upon the {{expiryPolicy=link-detach}} once the link is
detached.
The temporary queue _is_ deleted once the connection closes.
The attach establishing the temporary queue looks like this:
{noformat}
Attach{name=qpid-jms:temp-queue-creator:ID:d591b0c0-169d-4895-a227-e1e18c9709ab:1:1,handle=0,role=sender,sndSettleMode=unsettled,rcvSettleMode=first,source=Source{},target=Target{durable=none,expiryPolicy=link-detach,timeout=0,dynamic=true,dynamicNodeProperties={lifetime-policy=DeleteOnClose{}},capabilities=[temporary-queue]},incompleteUnsettled=false,initialDeliveryCount=0}
{noformat}
The problem seems to be that nothing acts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
