Yes i did use the same client id and publish message using Qos=1.
The point of this bug is server will not send missed messages to re-connected subscriptions until new publish messages to that topic. To re-produce the problem you have to wait the server disconnecting the connection by timeout. The log is: client some_id
has exeeded timeout, disconnectiong.
I also tested the same steps using Really Small Message Broker 1.2. Re-connected clients can receive missed messages immediately after they re-connected to Really Small Message Broker.
Hi Roger,
Yes i did use the same client id and publish message using Qos=1.
The point of this bug is server will not send missed messages to re-connected subscriptions until new publish messages to that topic. To re-produce the problem you have to wait the server disconnecting the connection by timeout. The log is: client some_id
has exeeded timeout, disconnectiong.
I also tested the same steps using Really Small Message Broker 1.2. Re-connected clients can receive missed messages immediately after they re-connected to Really Small Message Broker.
Thanks
David