Multiple subscribers, not all subscribers notified with QoS 1

Bug #1956842 reported by Christian Treber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mosquitto (Ubuntu)
New
Undecided
Unassigned

Bug Description

Mosquitto 2.0.14 on Ubuntu

I have three subscribers to a topic with QoS 1. When I publish with QoS 0, all subscribers get a publish. When I publish with QoS 1, only two subscribers get a publish.

QoS 0:

2022-01-08T21:43:01: Received PUBLISH from mqttspy-neko (d0, q0, r0, m0, 'generic/time', ... (15 bytes))
2022-01-08T21:43:01: Sending PUBLISH to acclock02 (d0, q0, r0, m0, 'generic/time', ... (15 bytes))
2022-01-08T21:43:01: Sending PUBLISH to acclock01 (d0, q0, r0, m0, 'generic/time', ... (15 bytes))
2022-01-08T21:43:01: Sending PUBLISH to mqttspy-neko (d0, q0, r0, m0, 'generic/time', ... (15 bytes))

This is fine; all three get a publish.

QoS 1:

2022-01-08T21:53:07: Received PUBLISH from mqttspy-neko (d0, q1, r0, m97, 'generic/time', ... (15 bytes))
2022-01-08T21:53:07: Sending PUBLISH to acclock01 (d0, q1, r0, m188, 'generic/time', ... (15 bytes))
>>>Note acclock02 missing<<<
2022-01-08T21:53:07: Sending PUBLISH to mqttspy-neko (d0, q1, r0, m43, 'generic/time', ... (15 bytes))
2022-01-08T21:53:07: Sending PUBACK to mqttspy-neko (m97, rc0)
2022-01-08T21:53:07: Received PUBACK from mqttspy-neko (Mid: 43, RC:0)
2022-01-08T21:53:07: Received PUBACK from acclock01 (Mid: 188, RC:0)

acclock02 is not being notified (exactly the same software/ hardware as acclock01, just two devices of the same kind).

I am missing something?

Christian

Revision history for this message
Christian Treber (ctreber) wrote :

Ay caramba, I meant "not all subscibers notified"

summary: - Multiple subscribers, only one subscriber notified with QoS 1
+ Multiple subscribers, not all subscribers notified with QoS 1
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.