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 #476314
status RESOLVED severity normal in component Mosquitto for 1.4
Reported in version 1.4 on platform All
Assigned to: Roger Light
Created attachment 256288
broker debug information
when ues Paho.MQTT to connect to broker with cleanSession flag set as false, and subscribe a topic with qos=1, and then disconnect, messages queued will not be received when the client reconnect to the broker, however, when i use a mqtt client with the same client id to connect then, the queued messages is received.
the attachment is the broker's debug information, the connection from localhost is created by mosquitto_pub or mosquitto_sub, and others is created by websocket(Paho.MQTT.Client).
On 2016-02-20 04:34:09 -0500, Christoph Krey wrote:
I just found and analyzed the same problem. Websockets subscriber does not receive
queued messages after cleansession=NO, disconnect, reconnect immediately after
reconnect, but only when a new message is published while Websockets subscriber is connected.
Steps to recreate:
0 connect with cleansession=NO, client gets sessionpresent=NO, subscribe QoS=1, abort
1 connect with cleansession=NO, client gets sessionpresent=YES, subscribe QoS=1, abort
2 connect with other client, publish message 1 QoS=1
3 connect with cleansession=NO, client gets sessionpresent=YES, subscribe QoS=1
MQTT now receives queued message, WS client doesn't
4 connect with cleansession=NO, client gets sessionpresent=YES, subscribe QoS=1
5 connect with other client, publish message 2 QoS=1
migrated from Bugzilla #476314
status RESOLVED severity normal in component Mosquitto for 1.4
Reported in version 1.4 on platform All
Assigned to: Roger Light
Original attachment names and IDs:
On 2015-09-01 09:28:00 -0400, Joking Young wrote:
On 2016-02-20 04:34:09 -0500, Christoph Krey wrote:
On 2016-02-20 04:35:04 -0500, Christoph Krey wrote:
On 2016-03-05 17:38:57 -0500, Roger Light wrote:
On 2016-03-06 09:20:15 -0500, Christoph Krey wrote:
On 2016-03-06 09:23:04 -0500, Christoph Krey wrote:
On 2016-03-06 09:40:57 -0500, Roger Light wrote:
On 2016-03-06 12:40:23 -0500, Christoph Krey wrote:
On 2016-03-06 12:45:03 -0500, Christoph Krey wrote:
On 2016-03-06 14:51:01 -0500, Roger Light wrote:
On 2016-03-07 05:06:14 -0500, Christoph Krey wrote:
On 2016-03-07 06:14:48 -0500, Roger Light wrote:
On 2016-03-10 01:53:04 -0500, Joking Young wrote:
The text was updated successfully, but these errors were encountered: