MQTT plugin and keep alive

[Antoine Galataud]

Hi all,

We're currently running RabbitMQ 3.4.4. We use MQTT plugin to communicate with an embedded device for which we implemented a MQTT client (C);

We had full satisfaction so far, except that it seems setting the keep alive header has no effect on server side: server should disconnect the client when reached, as stated by the specification.

We don't see anything like this, neither on client connection state nor in server logs.

For information: when testing with Paho (java version), Paho is doing all the work and checks that ping responses are received, if not disconnects.

Any help would be appreciated

Thanks in advance

Antoine

[Michael Klishin]

 On 25 February 2015 at 13:56:18, Antoine Galataud (antoine....@gmail.com) wrote:
> We had full satisfaction so far, except that it seems setting
> the keep alive header has no effect on server side: server should
> disconnect the client when reached, as stated by the specification.
> We don't see anything like this, neither on client connection
> state nor in server logs.
>
> For information: when testing with Paho (java version), Paho
> is doing all the work and checks that ping responses are received,
> if not disconnects.

Keep-alive should be supported. Do you have a small test case we can use to reproduce?
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Antoine Galataud]

Hi Michael,

Thanks for the quick answer. 

My mistake. A problem on our side. We fixed it  and it's now working like a charm. We get messages like:

closing MQTT connection "X.X.X.X:55941 -> X.X.X.X:1883" (keepalive timeout)

Thanks

Antoine

[Michael Klishin]

 On 26 February 2015 at 12:44:53, Antoine Galataud (antoine....@gmail.com) wrote:
> Thanks for the quick answer.
> My mistake. A problem on our side. We fixed it and it's now working
> like a charm. We get messages like:
>
> closing MQTT connection "X.X.X.X:55941 -> X.X.X.X:1883" (keepalive
> timeout)

Antoine,

Thank you for getting back to us. May I ask what was the issue? Any way RabbitMQ MQTT plugin
can help you notice such things quicker?

[saurabh gigras]

Hi I am facing exactly similar issue.

How do I make my rabbit-mqtt broker react to the keep-alive sent in connect request by the MQTT publisher?

Can you let me know in case i have to configure or take care of any parameter on rabbitmq broker?

regards

Saurabh