[
https://issues.apache.org/jira/browse/AMQ-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-4719.
-----------------------------
Resolution: Fixed
Link Stealing is enabled now by default for MQTT transport(s) -
AMQP is tricky - as enabling it will break JMS semantics for JMS over AMQP
clients - so left to the user to decide - e.g. in the broker config enable link
stealing:
<transportConnector name="nio" uri="nio://0.0.0.0:61616?allowLinkStealing=true
"/>
> 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.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.1#6144)
