You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Lorenz Quack (JIRA)" <ji...@apache.org> on 2017/02/02 14:46:53 UTC
[jira] [Commented] (QPID-7659) [Java Broker, AMQP 1.0] Support Link
stealing
[ https://issues.apache.org/jira/browse/QPID-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849998#comment-15849998 ]
Lorenz Quack commented on QPID-7659:
------------------------------------
When implementing this great care must be taken to be thread-safe.
There is an inherent danger of dead-locking when connection "A" tries to steal Link "foo" from connection "B" while connection "B" tries to steal Link "bar" from connection "A".
> [Java Broker, AMQP 1.0] Support Link stealing
> ---------------------------------------------
>
> Key: QPID-7659
> URL: https://issues.apache.org/jira/browse/QPID-7659
> Project: Qpid
> Issue Type: Task
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-7.0
>
>
> Currently, the broker does not support Link stealing as specified by the AMQP 1.0 specification (section 2.6.1).
> This means that Link uniqueness is not properly enforced.
> This also breaks the JMS bindings that rely on Link uniqueness to enforce things like uniqueness of ClientIds.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org