You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MQTT v5: outbound QoS 1/2 deliveries ignore the client's Receive Maximum #3281
A v5 client can advertise a Receive Maximum in CONNECT: the most QoS 1 and QoS 2 PUBLISHes it will accept unacknowledged. Harper ignores it for outbound deliveries and only slows a subscriber once more than 100 are pending (AWAITING_ACKS_HIGH_WATER_MARK in server/DurableSubscriptionsSession.ts). A client that advertises fewer, say 10, receives more than 10 in flight, which violates MQTT-3.3.4-9; a strict client may disconnect with 0x93.
main behaves the same for QoS 1. #3263 added the server-side Receive Maximum for inbound QoS 2 but not this direction. Possible direction: read properties.receiveMaximum from CONNECT and hold back deliveries while that many await PUBACK/PUBREC.
Reproduced on harper-pro 5.4.0-beta.2, on a single node and on a 2-region cluster.
A packet-level MQTT v5 client connects with receiveMaximum: 2, subscribes to a table topic at QoS 1, and never sends PUBACK. Ten QoS 1 messages are then published to that topic. The server sends all 10 PUBLISHes without waiting for an acknowledgement, where [MQTT-3.3.4-9] allows 2. The result is the same on both setups.
The AWAITING_ACKS_HIGH_WATER_MARK slowdown only starts after 100 pending deliveries. For a clean-session QoS 1 subscription, deliveries without an upstream acknowledge aren't tracked in awaitingAcks at all, so nothing counts against the client's limit.
Activity
maurice-harper commentedon Nov 10, 2026
Reproduced on harper-pro 5.4.0-beta.2, on a single node and on a 2-region cluster.
A packet-level MQTT v5 client connects with
receiveMaximum: 2, subscribes to a table topic at QoS 1, and never sends PUBACK. Ten QoS 1 messages are then published to that topic. The server sends all 10 PUBLISHes without waiting for an acknowledgement, where [MQTT-3.3.4-9] allows 2. The result is the same on both setups.The
AWAITING_ACKS_HIGH_WATER_MARKslowdown only starts after 100 pending deliveries. For a clean-session QoS 1 subscription, deliveries without an upstream acknowledge aren't tracked inawaitingAcksat all, so nothing counts against the client's limit.