Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

protocol errors for QoS1 and Qos2 in a congested environment #10

Closed
ralight opened this issue Mar 15, 2016 · 0 comments
Closed

protocol errors for QoS1 and Qos2 in a congested environment #10

ralight opened this issue Mar 15, 2016 · 0 comments

Comments

@ralight
Copy link
Contributor

ralight commented Mar 15, 2016

migrated from Bugzilla #486892
status CLOSED severity major in component Mosquitto for 1.4
Reported in version 1.4 on platform All
Assigned to: Roger Light

On 2016-01-30 11:05:20 -0500, Christoph Krey wrote:

Broker 1.4.4
Client libmosquitto 1.4.7

Congestion situation arises because initial SUBSCRIBE triggers the transmission
of about 1000 retained messages, each about 1500 bytes long.

Broker publishes Qos1 and Qos2 messages...
Client repeats PUBRECs although PUBREL was send by broker and PUBCOMP received, leading to connection close

connection re-established is closed repeatedly because of unexpected PUBREL received by broker

This situation repeats until broker decides to answer the PUBRECs with PUBRELs instead of closing the connection.

After reconnection, broker re-sends (dup=1) Qos1 messages, but sends some of them 2 or 3 times.

After reconnection, broker sends (dup=0) multiple Qos1 messages with the same messageId
without receiving PUBACK in between.

Log will be sent directly to roger

On 2016-02-11 16:55:19 -0500, Roger Light wrote:

I've not yet had chance to analyse this fully, but am closing this because you've accidently submitted two reports.

*** This bug has been marked as a duplicate of bug 486891 ***

@ralight ralight closed this as completed Mar 15, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant