You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Rich P <te...@hotmail.com> on 2014/07/06 21:08:05 UTC
RE: MQTT Link Stealing
After testing the scenario below with version 5.10.0, I've found that the allowLinkStealing="true" appears to work properly only for the *first* reconnect; if the same MQTT client reconnects a second time (using the same client-id) the previous connection is not closed and I get the following error:
WARN | Failed to register MBean org.apache.activemq:type=Broker,brokerName=broker1,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=test1
Mark -- Are you seeing this in your environment?
Does anyone know of a way to prevent or work around this?
Thanks!
Rich
> Date: Sun, 22 Jun 2014 04:04:13 -0700
> From: tingenek@gmail.com
> To: users@activemq.apache.org
> Subject: Re: MQTT Link Stealing
>
> mtakahashi,
>
> Ok, now I’ve got it working using the following:
>
> <transportConnector name="mqtt" allowLinkStealing="true" uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
>
> I’ll do some further testing, but that seems to have fixed it. Brief dropping of the connection is a very common problem with phones was well as IoT devices using MQTT, so this is good news for use of ActiveMQ as a broker as I’m a big fan of Camel.
>
> Rgds,
>
> Mark Lawson
> Senior Technical Architect
> Staffordshire and West Midlands
> Community Rehabilitation Company
> mark.lawson@swm.probation.gsi.gov.uk
> [sent from home email]
>
>
> On 22 Jun 2014, at 11:02, mtakahashi [via ActiveMQ] <ml...@n4.nabble.com> wrote:
>
> > Hi,
> >
> >
> > Transport options should be a XML attribute of the "transportConnector" element, like following.
> >
> > <transportConnector name="mqtt" allowLinkStealing=true uri="mqtt://0.0.0.0:1883?maximumConnections=1000&wireFormat.maxFrameSize=104857600"/>
> >
> > See the last line of this page.
> > http://activemq.apache.org/configuring-transports.html
> >
> > Regards,
> > mtakahashi
> >
> > If you reply to this email, your message will be added to the discussion below:
> > http://activemq.2283324.n4.nabble.com/MQTT-Link-Stealing-tp4682263p4682364.html
> > To unsubscribe from MQTT Link Stealing, click here.
> > NAML
>
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/MQTT-Link-Stealing-tp4682263p4682365.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
RE: MQTT Link Stealing
Posted by Shobhana <sh...@quickride.in>.
I am using version 5.11.1 with Eclipse Paho MQTT Client and find the same
issue in this version too. By default, for MQTT, allowLinkStealing is set to
true. But I see hundreds of following messages in AMQ logs :
2015-09-10 13:21:47,544 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=qrserverchat
| org.apache.activemq.broker.jmx.ManagedTransportConnection | ActiveMQ
Transport: tcp:///52.74.19.21:56042@1883
2015-09-10 13:21:47,543 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=qrserverchat
| org.apache.activemq.broker.jmx.ManagedTransportConnection | ActiveMQ
Transport: tcp:///52.74.19.21:56044@1883
2015-09-10 13:21:47,543 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=qrserverchat
| org.apache.activemq.broker.jmx.ManagedTransportConnection | ActiveMQ
Transport: tcp:///52.74.19.21:56008@1883
2015-09-10 13:21:47,543 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=qrserverchat
| org.apache.activemq.broker.jmx.ManagedTransportConnection | ActiveMQ
Transport: tcp:///52.74.19.21:56013@1883
2015-09-10 13:21:47,543 | WARN | Failed to register MBean
org.apache.activemq:type=Broker,brokerName=localhost,connector=clientConnectors,connectorName=mqtt,connectionViewType=clientId,connectionName=qrserverchat
| org.apache.activemq.broker.jmx.ManagedTransportConnection | ActiveMQ
Transport: tcp:///52.74.19.21:56009@1883
2015-09-10 13:21:47,528 | WARN | Stealing link for clientId qrserverchat
>From Connection Transport Connection to: tcp://52.74.19.21:56241 |
org.apache.activemq.broker.region.RegionBroker | ActiveMQ Transport:
tcp:///52.74.19.21:56229@1883
2015-09-10 13:21:47,526 | WARN | Stealing link for clientId qrserverchat
>From Connection Transport Connection to: tcp://52.74.19.21:56235 |
org.apache.activemq.broker.region.RegionBroker | ActiveMQ Transport:
tcp:///52.74.19.21:56241@1883
2015-09-10 13:21:47,526 | WARN | Stealing link for clientId qrserverchat
>From Connection Transport Connection to: tcp://52.74.19.21:56237 |
org.apache.activemq.broker.region.RegionBroker | ActiveMQ Transport:
tcp:///52.74.19.21:56235@1883
2015-09-10 13:21:47,525 | WARN | Stealing link for clientId qrserverchat
>From Connection Transport Connection to: tcp://52.74.19.21:56203 |
org.apache.activemq.broker.region.RegionBroker | ActiveMQ Transport:
tcp:///52.74.19.21:56237@1883
Strangely, this problems starts after running AMQ for about 6 hours and AMQ
does not recover from this issue; the only solution is to restart it!
Does anyone know any solution or workaround to get rid of this problem?
Thanks,
Shobhana
--
View this message in context: http://activemq.2283324.n4.nabble.com/MQTT-Link-Stealing-tp4682263p4701866.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.