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

Michael Klishin mklishin at gopivotal.com
Mon Jul 28 02:48:46 BST 2014

 On 27 July 2014 at 18:36:16, brydev (bcliffe at gmail.com) wrote:
> > 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.

We will investigate but the fundamental issue seems to be the same on both ends:
both peers do not notice connection loss.

Staff Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list