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
migrated from Bugzilla #467304
status UNCONFIRMED severity normal in component Mosquitto for 1.4
Reported in version 1.4 on platform PC
Assigned to: Roger Light
On 2015-05-14 02:46:43 -0400, jsaak jsaak wrote:
Bridge connection enters a connect-disconnect loop when incomplete QoS 2 publish, and local broker fails to persist for any reason.
Scenario:
local mosq publishes QoS2 to remote mosq
local mosq dies (fails to persist)
local mosq restarts with "clean_session false"
local mosq reestabilishes bridge connection to remote mosq
remote mosq replies with PUBREC
local mosq does not find the corresponding message in the DB, gives error
local mosq disconnect bridge connection
goto 4.
My proposed solution is that change 6.
If it does not find the mid in the DB reply anyway, with a WARNING.
We see the same in our production environment with the latest version.
Unfortunately this seems endemic in MQTT implementations: see also eclipse/paho.mqtt.java#27 for the same bug in the java client
Under the right circumstances this happens for most/all acknowledgements so PUBCOMP and PUBACK can probably trigger the same behaviour (Possibly SUBACKs as well)
migrated from Bugzilla #467304
status UNCONFIRMED severity normal in component Mosquitto for 1.4
Reported in version 1.4 on platform PC
Assigned to: Roger Light
On 2015-05-14 02:46:43 -0400, jsaak jsaak wrote:
The text was updated successfully, but these errors were encountered: