Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When a client reconnects it don't receive queued messages #12

Open
ralight opened this issue Mar 15, 2016 · 0 comments
Open

When a client reconnects it don't receive queued messages #12

ralight opened this issue Mar 15, 2016 · 0 comments
Labels

Comments

@ralight
Copy link
Contributor

ralight commented Mar 15, 2016

migrated from Bugzilla #430788
status UNCONFIRMED severity normal in component RSMB for ---
Reported in version unspecified on platform PC
Assigned to: Ian Craggs

Original attachment names and IDs:

On 2014-03-20 08:24:30 -0400, Daniel Nascimento wrote:

Steps to reproduce:
1- Connects a MQTT-SN client and subscribe in a topic
2- Disconnect it
3- Post some messages in the topic that the client was subcribed
4- Reconnect the client

After applying the patch for bug # 430733 and # 430737 the RSMB will queue messages for the client, but it don't deliver them.

On 2014-03-20 08:25:24 -0400, Daniel Nascimento wrote:

Created attachment 241054
Fix the rule to determine a pre existing client

On 2014-03-20 08:27:15 -0400, Daniel Nascimento wrote:

Created attachment 241055
Remove a rule restricting the deliver for a client if a outbound greater than zero

I didn't understand this rule so I don't know commenting it is the right fix.

On 2014-03-20 09:29:51 -0400, Daniel Nascimento wrote:

If the broker is running with "persistence true" these patches won't fix the problem.

@ralight ralight added the bug label Mar 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant