-
-
Notifications
You must be signed in to change notification settings - Fork 507
Use persistence MongoDB, but there is a problem subscriptions #80
Conversation
Probably you are hitting some behaviors not covered by the unit tests of Mosca. It's fine to iron out bugs. I tested the issue and it's present also without Mongo, so it's something else. |
Can you try https://github.com/mcollina/mosca/tree/fix-80 and see if it solves this issue? Thanks. |
Ok, everything should be fixed for all persistence. |
Nice work! |
Otherwise we will queue offline messages when they are not due.
It should be fixed with the latest commit. Can you please check? |
I tried again.
The 5 step, client is online. |
Ok, I got the steps to reproduce it reliably here. |
I have updated this branch with the new fix. Let me know if it works. Thanks for reporting this! In any case, it will be released as 0.15.0. |
Nice! |
Use persistence MongoDB, but there is a problem subscriptions
Released as 0.14.4. |
I used the DEMO offline mode code.
It worked well the first time.
But when I reload the page, subscriptions collection will insert a new record.
So the same clientId has two records in subscriptions collection.
Now I publish a message and connect client, we will get two offline messages.
What's wrong with me?
Thank you.