Why is message received over and over again?

Question

Why is message received over and over again?

ddobric opened this issue 6 years ago · comments

By following you example, I have implemented subscriber as shown below:

this.m_MqttClient.MessageStream
.Where(msg => msg.Topic == this.m_RcvTopic)
.Subscribe(async msg => {
await msgReceiver?.Invoke(msg.Payload);

The message is sent by using this code:
await this.m_MqttClient.PublishAsync(new MqttApplicationMessage(this.m_SendTopic, message), MqttQualityOfService.ExactlyOnce);

The message is correctly sent and received, but receiving of the same message does not stop.
The message is received over and over again.
What is the correct way to reliably complete receiving of the message?

Thanks

Daniel Cazzulino · Answer 1 · Sun Aug 12 2018 10:19:37 GMT+0800 (China Standard Time)

Are SendTopic and RcvTopic the same? Have you subscribed the client with that topic before subscribing to the observable? What is the server being used? Is it System.Mqtt.Server too or a third party?

Thanks!

Dr. Damir Dobric · Answer 2 · Mon Aug 20 2018 16:26:38 GMT+0800 (China Standard Time)

It looks as this would happen if publisher and receiver use same ClientID. This is for sure not a production case (it happened during invalid unit test configuration), but I'm not sure if it is correct.

Daniel Cazzulino · Answer 3 · Tue Aug 21 2018 09:46:17 GMT+0800 (China Standard Time)

The second connection using the same client ID should cause the previous one to be forcefully disconnected, according to the spec. I believe that is currently the case, right @mauroa?

Dr. Damir Dobric · Answer 4 · Fri Aug 24 2018 21:56:18 GMT+0800 (China Standard Time)

It does not behave this way.
Second does not cause the first one to be disconnected. First one is continuously receiving the message.
To me this does not look correct.

Mauro Agnoletti · Answer 5 · Fri Aug 24 2018 22:02:34 GMT+0800 (China Standard Time)

Can you please try changing the Quality of Service to a lower value? (either 0 or 1). You are using QoS 2 in your samples (MqttQualityOfService.ExactlyOnce). It’s just to discard an issue with it.
Thanks.

Daniel Cazzulino · Answer 6 · Fri Aug 24 2018 22:06:01 GMT+0800 (China Standard Time)

Are you using this MQTT implementation for both client and server? If so, can you provide the full failing unit test so we can repro?

Thanks!

Dr. Damir Dobric · Answer 7 · Thu Aug 30 2018 14:32:43 GMT+0800 (China Standard Time)

I'm using MqttQualityOfService.ExactlyOnce
Use same library for client and server in the same process inside of unit tests and also in different processes.

As I mentioned, the reason was using of same ClientID for publisher and subscriber.

daspuru · Answer 8 · Sat Sep 01 2018 05:57:23 GMT+0800 (China Standard Time)

Hi, I am testing the server and the client (this implementation), and have a similar issue. When I suscribe to a topic, and then send only one message to that topic, the message is received and received infinitely at intervals for about 5 seconds. It is the same client, in the same app. First I suscribe to the topic and then send the message.

If I send the message from another client, the message just arrives once, but sending it from the same client makes this weird behavior...

Thanks a lot!

daspuru · Answer 9 · Sat Sep 01 2018 06:40:59 GMT+0800 (China Standard Time)

Hi all, I fixed the issue staring the server with the same configuration as the client (QoS 2), as I was not introducing any parameter in the MqttServer.Create() method.

Now it seems to work great! :)

Dr. Damir Dobric · Answer 10 · Tue Sep 04 2018 03:10:30 GMT+0800 (China Standard Time)

Good job 👍
Which nuget version contains the fix?

Roman Novotny · Answer 11 · Thu Jan 10 2019 16:08:45 GMT+0800 (China Standard Time)

I think it still not working correctly on version I get from nuget in visual studio. I still get one topic after a while. And dont get nothing on the beginning. And when I use Guid as ClientId it is not working at all. So I came back to M2Mqtt