<div dir="ltr">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.<div>
<br></div><div><div>private boolean isConnected() {</div><div><span class="" style="white-space:pre">             </span>if(mStarted && mClient != null && !mClient.isConnected()) {</div><div><span class="" style="white-space:pre">                        </span>Log.i(DEBUG_TAG,"Mismatch between what we think is connected and what is connected");</div>
<div><span class="" style="white-space:pre">            </span>}</div></div><div><br></div><div>So I can't tell if the old, new or both connections are disconnected from the broker.  </div></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Sun, Jul 27, 2014 at 3:25 PM, Michael Klishin-2 [via RabbitMQ] <span dir="ltr"><<a href="/user/SendEmail.jtp?type=node&node=36905&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>></span> wrote:<br>
<blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">

        <br><br>On 27 July 2014 at 17:07:14, brydev (<a href="http://user/SendEmail.jtp?type=node&node=36903&i=0" rel="nofollow" link="external" target="_blank">[hidden email]</a>) wrote:
<div><div class='shrinkable-quote'><br>> > I have tested the lower heartbeat interval, having it as low  
<br>> as 1 second but
<br>> the RabbitMQ broker is still disconnecting the new connection  
<br>> after an
<br>> attempt in reconnect. Having a heartbeat interval this low also  
<br>> affects the
<br>> power usage on the device. I was wondering maybe a possible solution  
<br>> could
<br>> be a policy whereby if there is a duplicate connection attempt  
<br>> on the broker
<br>> to then disconnect the oldest connection.
</div></div></div>MQTT 3.1 requires brokers to disconnect an old connection with the same
<br><div class="">client id but (as I understand it) only after successful authentication.
<br><br>Are you saying that it's not what you're observing? 
<br></div><div class="">--  
<br>MK  
<br><br>Staff Software Engineer, Pivotal/RabbitMQ
<br></div><div class="">_______________________________________________
<br>rabbitmq-discuss mailing list has moved to <a href="https://groups.google.com/forum/#!forum/rabbitmq-users" rel="nofollow" link="external" target="_blank">https://groups.google.com/forum/#!forum/rabbitmq-users</a>,
<br>please subscribe to the new list!
<br><br><a href="http://user/SendEmail.jtp?type=node&node=36903&i=1" rel="nofollow" link="external" target="_blank">[hidden email]</a>
<br><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" rel="nofollow" link="external" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>

        
        
        
        <br>
        <br>
        </div><hr noshade size="1" color="#cccccc">
        <div style="color:#444;font:12px tahoma,geneva,helvetica,arial,sans-serif"><div class="">
                <div style="font-weight:bold">If you reply to this email, your message will be added to the discussion below:</div>
                </div><a href="http://rabbitmq.1065348.n5.nabble.com/MQTT-plugin-QoS-1-Android-not-consuming-on-reconnect-tp36888p36903.html" target="_blank" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/MQTT-plugin-QoS-1-Android-not-consuming-on-reconnect-tp36888p36903.html</a>
        </div><div class="HOEnZb"><div class="h5">
        <div style="color:#666;font:11px tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em">
                
                To unsubscribe from MQTT plugin, QoS 1, Android, not consuming on reconnect, <a href="" target="_blank" rel="nofollow" link="external">click here</a>.<br>

                <a href="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" rel="nofollow" style="font:9px serif" target="_blank" link="external">NAML</a>
        </div></div></div></blockquote></div><br></div>


        
        
        
<br/><hr align="left" width="300" />
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/MQTT-plugin-QoS-1-Android-not-consuming-on-reconnect-tp36888p36905.html">Re: MQTT plugin, QoS 1, Android, not consuming on reconnect</a><br/>
Sent from the <a href="http://rabbitmq.1065348.n5.nabble.com/">RabbitMQ mailing list archive</a> at Nabble.com.<br/>