[rabbitmq-discuss] MQTT plugin, QoS 1, Android, not consuming on reconnect

Sun Jul 27 15:35:03 BST 2014

The service on the application is unable to reconnect again after the
duplicate id is detected. It reconnects sometimes but if it does it doesn't
consume the missed messages on the queue. The log doesn't give me anything
else besides duplicate client id disconnected. And my device is throwing
the following error on loop and is unable to reconnect.

private boolean isConnected() {
if(mStarted && mClient != null && !mClient.isConnected()) {
Log.i(DEBUG_TAG,"Mismatch between what we think is connected and what is
connected");
}

So I can't tell if the old, new or both connections are disconnected from
the broker.

On Sun, Jul 27, 2014 at 3:25 PM, Michael Klishin-2 [via RabbitMQ] <
ml-node+s1065348n36903h56 at n5.nabble.com> wrote:

>
>
> On 27 July 2014 at 17:07:14, brydev ([hidden email]
> <http://user/SendEmail.jtp?type=node&node=36903&i=0>) wrote:
>
> > > I have tested the lower heartbeat interval, having it as low
> > as 1 second but
> > the RabbitMQ broker is still disconnecting the new connection
> > after an
> > attempt in reconnect. Having a heartbeat interval this low also
> > affects the
> > power usage on the device. I was wondering maybe a possible solution
> > could
> > be a policy whereby if there is a duplicate connection attempt
> > on the broker
> > to then disconnect the oldest connection.
>
> MQTT 3.1 requires brokers to disconnect an old connection with the same
> client id but (as I understand it) only after successful authentication.
>
> Are you saying that it's not what you're observing?
> --
> MK
>
> Staff Software Engineer, Pivotal/RabbitMQ
> _______________________________________________
> rabbitmq-discuss mailing list has moved to
> https://groups.google.com/forum/#!forum/rabbitmq-users,
> please subscribe to the new list!
>
> [hidden email] <http://user/SendEmail.jtp?type=node&node=36903&i=1>
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://rabbitmq.1065348.n5.nabble.com/MQTT-plugin-QoS-1-Android-not-consuming-on-reconnect-tp36888p36903.html
>  To unsubscribe from MQTT plugin, QoS 1, Android, not consuming on
> reconnect, click here
> <http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=36888&code=YmNsaWZmZUBnbWFpbC5jb218MzY4ODh8MTQ1NzU4Njg1Mg==>
> .
> NAML
> <http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>

--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/MQTT-plugin-QoS-1-Android-not-consuming-on-reconnect-tp36888p36905.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140727/1b4424a1/attachment.html>