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
Type messages one by one and see that they are received. No simulate some kind of network failure like the broker going away
sudo iptables -A OUTPUT -d <broker_IP>/32 -j REJECT
Now type some messages again in above window so that mosquitto_pub should deliver it after connection is re-established. However after some time an error appears Error: Publish returned 4, disconnecting.
mosquitto_pub exits and all messages after connection problems are lost.
So is the MQTT specification unclear or is this a bug in mosquitto_pub? Personally I think with QOS 1 message should get queued up to a configurable limit before messages get dropped.
The text was updated successfully, but these errors were encountered:
According to https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/
So according to specification sender stores messages until it is successfully delivered.
Execute
mosquitto_pub -t test -h <host> -u <user> -P <PW> -l -q 1
Type messages one by one and see that they are received. No simulate some kind of network failure like the broker going away
sudo iptables -A OUTPUT -d <broker_IP>/32 -j REJECT
Now type some messages again in above window so that mosquitto_pub should deliver it after connection is re-established. However after some time an error appears
Error: Publish returned 4, disconnecting.
mosquitto_pub exits and all messages after connection problems are lost.
So is the MQTT specification unclear or is this a bug in mosquitto_pub? Personally I think with QOS 1 message should get queued up to a configurable limit before messages get dropped.
The text was updated successfully, but these errors were encountered: