You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Dhiraj Bokde (JIRA)" <ji...@apache.org> on 2014/07/28 23:33:38 UTC

[jira] [Reopened] (AMQ-4719) Enable "Link Stealing" as an option on a Connector

     [ https://issues.apache.org/jira/browse/AMQ-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dhiraj Bokde reopened AMQ-4719:
-------------------------------


The option was not set by default in MQTTSslTransportFactory. 

> 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)