You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/03/01 18:24:18 UTC
[jira] [Comment Edited] (QPID-6703) Add optional mechanism to
associate a temporary queue lifetime with that of it connection
[ https://issues.apache.org/jira/browse/QPID-6703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174055#comment-15174055 ]
Keith Wall edited comment on QPID-6703 at 3/1/16 5:23 PM:
----------------------------------------------------------
Hi Rob,
I made a couple of tidy up within the tests.
Now the temporary queue's lifetime follows JMS semantics, I think the no-op in AMQSession_0_8#deleteTemporaryDestination can be removed (iff _connection.getDelegate().isQueueLifetimePolicySupported()) and we can respect the user's wishes to delete the queue. Test TemporaryQueueTest#testExplictTemporaryQueueDeletion can be changed to remove the if .. 0-10 bracket too. It also means that all paragraphs within docbook JMS-Clinet-Understanding.xml#JMS-Client-0-8-Client-Understanding-Session-TemporaryQueues) apart from the note about the naming of the temporary queue can be removed.
was (Author: k-wall):
Hi Rob,
I made a couple of tidy up within the tests.
Now the temporary queue's lifetime follows JMS semantics, I think the no-op in AMQSession_0_8#deleteTemporaryDestination can be removed (iff _connection.getDelegate().isQueueLifetimePolicySupported()) and we can respect the user's wishes to delete the queue. It also means that all paragraphs within docbook JMS-Clinet-Understanding.xml#JMS-Client-0-8-Client-Understanding-Session-TemporaryQueues) apart from the note about the naming of the temporary queue can be removed.
> Add optional mechanism to associate a temporary queue lifetime with that of it connection
> -----------------------------------------------------------------------------------------
>
> Key: QPID-6703
> URL: https://issues.apache.org/jira/browse/QPID-6703
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker, Java Client
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.1
>
>
> For JMS specification compliance the Java Broker should be able to have the lifetime of an temporary queue bound to the lifetime of the connection that created it.
> This is not possible with strict AMQP 0-8..0-10, which have different notions of auto delete lifetime, but would be possible with the use of a vendor-specific queue declare property.
> The client should be changed to detect whether the argument is supported at connection negotiation time, and iff true, should include the argument when declaring new temporary queues.
--
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