search

adsetiawan / moquette-mqtt

Automatically exported from code.google.com/p/moquette-mqtt
Apache License 2.0
0 stars 0 forks source link

messageID problem #44

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. client1 connect server for subscribe topic 'topic1'  using qos2 , then 
disconnect server 
2. client2 send two message 'hello1' 'hello2'  to 'topic1' 
3. the client connect server again and receive message 'hello1' twice but not 
receive 'hello2'

What is the expected output? What do you see instead?
client1 receive 'hello1' 'hello2'

      messageId =1 ?

Original issue reported on code.google.com by lium...@liba.com on 14 May 2014 at 6:51

GoogleCodeExporter commented 8 years ago 
We have seen a similar problem, where multiple messages are published on a 
single topic from a single publisher with QoS 2, and when they are delivered to 
the single subscriber (also QoS 2), the message payloads differ, but the 
message IDs are all identical. Needless to say, this confuses the subscriber.

Packet capture showing this behavior is attached.

Original comment by yoto...@gmail.com on 15 May 2014 at 12:35

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by selva.an...@gmail.com on 20 May 2014 at 4:18

GoogleCodeExporter commented 8 years ago 
Hi,
I've created an integration test to reproduce the case, 
(https://code.google.com/p/moquette-mqtt/source/detail?r=80eb7d7cea19ef94a2eef46
59d4c7bbb5cea6072) but the test work correctly.

@liumiao please could you provide more details on the Moquette version you are 
using?

@yotommy this sounds quite similar to the issue #30, is it the same?It happens 
also with Moquette v0.5 and with the latest snapshot?

Thanks a lot for your support, actually reproduce the bug, so if you could help 
reproduce or understand it's very appreciated.

 Andrea

Original comment by selva.an...@gmail.com on 20 May 2014 at 9:14

GoogleCodeExporter commented 8 years ago

Original comment by selva.an...@gmail.com on 6 Jun 2014 at 10:29

GoogleCodeExporter commented 8 years ago 
I see that this issue been marked as fixed, but has it been checked in?  I 
didn't see anything about it in the change file from the latest GIT update.

Original comment by josh.auz...@gmail.com on 9 Jun 2014 at 8:23