Skip to content
This repository has been archived by the owner on Feb 11, 2020. It is now read-only.

Duplicate message delivery for multiple subscriptions on nested topics #426

Open
psorowka opened this issue Mar 1, 2016 · 6 comments
Open

Comments

@psorowka
Copy link
Contributor

psorowka commented Mar 1, 2016

I stumbled over the following issue.

When subscribing with a single client to a mosca instance to two nested topics, e.g.

mosquitto_sub -t some/thing/# -t some/thing/specific

And subsequently publishing to

mosquitto_pub -t some/thing/specific -m value

The client will receive the message twice (with different message ids).

I am not absolutely sure whether this is expected or not; I haven't found anything clear about it in the mqtt spec. however, at least cross-checking against test.mosquitto.org did not show this behavior.

@mcollina is that a mosca or ascoltatori topic? I think in either case the fix shouldn't be too tough and I could create a PR in a few days..

@mcollina
Copy link
Collaborator

mcollina commented Mar 1, 2016

on which backend?

There is a whole dedupe logic, so it is a bug
Il giorno mar 1 mar 2016 alle 09:47 Peter Sorowka notifications@github.com
ha scritto:

I stumbled over the following issue.

When subscribing with a single client to a mosca instance to two nested
topics, e.g.

mosquitto_sub -t some/thing/# -t some/thing/specific

And subsequently publishing to

mosquitto_pub -t some/thing/specific -m value

The client will receive the message twice (with different message ids).

I am not absolutely sure whether this is expected or not; I haven't found
anything clear about it in the mqtt spec. however, at least cross-checking
against test.mosquitto.org did not show this behavior.

@mcollina https://github.com/mcollina is that a mosca or ascoltatori
topic? I think in either case the fix shouldn't be too tough and I could
create a PR in a few days..


Reply to this email directly or view it on GitHub
#426.

@psorowka
Copy link
Contributor Author

psorowka commented Mar 1, 2016

Ah.. sorry didn't even think about it could be backend specific. This is on redis.

And seems to be redis specific as well, at least it doesn't happen with mongo or memory backend

@mcollina
Copy link
Collaborator

mcollina commented Mar 1, 2016

Confirmed, it is redis specific.

@psorowka
Copy link
Contributor Author

psorowka commented Mar 1, 2016

do you have an instant clue? I'm not familiar with the dedupe logic yet so would have to do some debugging first to understand things..

@psorowka
Copy link
Contributor Author

psorowka commented Mar 1, 2016

mhh okay. unfortunately i have no capacities today

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants