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.law...@swm.probation.gsi.gov.uk
[sent from home email]
On 22 Jun 2014, at 11:02, mtakahashi [via ActiveMQ]
<ml-node+s2283324n468236...@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.
