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

Michael Klishin mklishin at gopivotal.com
Fri Jul 25 20:41:28 BST 2014

On 25 July 2014 at 23:09:44, brydev (bcliffe at gmail.com) wrote:
> > I've implemented a Paho MQTT service in Android which is currently 
> unable to
> consume unacked messages upon reconnect to the RabbitMQ broker 
> with MQTT
> plugin. If I force the callback when the connectivity changes, 
> it will
> consume the missed messages.
> Sometimes forcing the callback will not work and the messages 
> remain unacked
> on the broker. Due to the unusual behaviour of when the message 
> consumes
> from the queue makes the service unreliable. The messages are 
> QoS 1.

What do you mean by "forcing the callback"?

> Also upon reconnect the messages will arrive as normal to the 
> device but the
> missed ones never get re-queued.
> The application is currently behaving fine when receiving messages 
> from a
> mosquitto broker so am I missing any implementation?
> Is this a bug or is there a setting I have possible missed for consuming 
> messages from my topic.

Can you post some example code that demonstrates the issue? What's in RabbitMQ log

Staff Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list