-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
"per_listener_settings true" causes messages for clients to no longer be stored #2618
Comments
The issue occurs in versions 2.0.12, 2.0.13, 2.0.14 and 2.0.15. |
I found the same Bug, for people who rely on the queueing of QOS 1 or 2 Messages this is a Showstopper for updating to the latest versions. Steps to reproduce:
Change the Setting to "false" and repeat You will get the queued messages! |
I've found the same issue today 2.0.14 and 2.0.15
test script
|
To emphasize the importance of this topic, I repeat what jh-profilsys-de already wrote above: "for people who rely on the queueing of QOS 1 or 2 Messages this is a Showstopper for updating to the latest versions" I think this problem affects a large group of users. Therefore, in my opinion, its priority should be increased. |
+1 |
I found this bug was introduced by the commit 7954215 |
related to #2526 |
revert commit 7954215
but I do not know other feed back and bugs this can create |
+1 took me quite a while to work out this was the cause! |
Reverting commit 7954215 |
I'm also having exactly the same issue. Here is my dockerized setup that reveals the problem, should be easy to reproduce: docker-compose.yml
mosquitto.conf (variant 1, fails with mosquitto >= 2.0.12)
mosquitto.conf (variant 2, works fine in all versions)
Run with different broker versions, using either variant 1 or 2 of the config:
Expected output is something like this:
Summary of my results ("OK" - HELLO received, "NOT OK" - HELLO not received on reconnect):
|
Anyone knows if there is any plans or progress on this bug? I would think having the option of queuing messages while at the same time having several differently configured listeners would be a major feature for many users. |
We also just encountered this in our project. Wasn't easy to find out that the issue of QoS 1 messages not being delivered properly was this (from my pov) unrelated config setting. |
After also running into this issue, I managed to track down the problem commit which came in 2.0.12: 7954215 This commit sets
I'm not sure how |
It looks like the original
The result without Another possible solution could be as below?
|
mosquitto broker version 2.0.15 (Oracle Linux 8)
Start mosquitto with the following configuration:
sys_interval 1
per_listener_settings true
listener 1883
allow_anonymous true
mosquitto_sub -p 1883 -v -t '$SYS/broker/clients/connected' -t '$SYS/broker/clients/total' -t '$SYS/broker/store/messages/count'
what leads to:
$SYS/broker/clients/total 1
$SYS/broker/clients/connected 1
$SYS/broker/store/messages/count 53
mosquitto_sub -p 1883 -q 2 -t test/# -d -c -i clientA
$SYS/broker/clients/connected 2
$SYS/broker/clients/total 2
stop client / ctrl-c / -> disconnect
$SYS/broker/clients/connected 1
mosquitto_pub -p 1883 -q 2 -t test/xxx -m "Testnachricht"
The count of messages should increment by 1 but is not !!!
mosquitto_sub -p 1883 -q 2 -t test/# -d -c -i clientA
Does not return the expected message !!!
Retry with
per_listener_settings false
Now it works like expected.
Thank You very much, Regards
Joachim Schachermayer
The text was updated successfully, but these errors were encountered: