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

[FIXED] Possible duplicate processing of a PubAck #131

Merged
merged 1 commit into from
Jan 12, 2017

Conversation

kozlovic
Copy link
Member

@kozlovic kozlovic commented Jan 9, 2017

It is possible that the client timeout at the same time that it
receives the pubAck from the server. It is acceptable to have
the client report a failure because it timed-out, even though
the ack has just been received, but it is not correct to invoke
the AckHandler twice for the same guid.

Also, the issue would cause serious problems for synchronous
Publish() calls. See issue report for details.

Resolves #130

It is possible that the client timeout at the same time that it
receives the pubAck from the server. It is acceptable to have
the client report a failure because it timed-out, even though
the ack has just been received, but it is not correct to invoke
the AckHandler twice for the same guid.

Also, the issue would cause serious problems for synchronous
Publish() calls. See issue report for details.

Resolves #130
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 83.883% when pulling ef5d22b on puback_processing into 0778981 on master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants