You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/03/01 18:05:18 UTC
[jira] [Commented] (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=15174028#comment-15174028 ]
ASF subversion and git services commented on QPID-6703:
-------------------------------------------------------
Commit 1733106 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1733106 ]
QPID-6703: Corrected a couple of superficial test issues and implemented test to ensure another connection could publish to a another's temporary queue
> 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