activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4719) Enable "Link Stealing" as an option on a Connector
Date Tue, 29 Jul 2014 02:20:41 GMT

    [ https://issues.apache.org/jira/browse/AMQ-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077297#comment-14077297
] 

Dhiraj Bokde commented on AMQ-4719:
-----------------------------------

Hi Surf, can you try adding the allowLinkStealing attribute as mentioned at http://activemq.apache.org/configuring-transports.html
in the transportConnector element in your broker.xml? 

> Enable "Link Stealing" as an option on a Connector
> --------------------------------------------------
>
>                 Key: AMQ-4719
>                 URL: https://issues.apache.org/jira/browse/AMQ-4719
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>            Reporter: Rob Davies
>            Assignee: Rob Davies
>             Fix For: 5.9.1, 5.10.0
>
>
> The JMS Spec states that connecting with a duplicate ClientID should throw an Exception.
However, for MQTT and AMQP specs "Link Stealing" where the last ClientID pushes out the older
connection with the same ClientID should be supported. ActiveMQ supports link stealing for
connections with a duplicate ConnectionID - though the ConnectionID is not something supported
by MQTT or AMQP. Make Link Stealing optional - so it can be set on by default for MQTT and
AMQP TransportConnectors



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message