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

Class C C2D message handler should close the connection after sending the message #1585

Open
spygi opened this issue Mar 3, 2022 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@spygi
Copy link
Contributor

spygi commented Mar 3, 2022

There is a potential race between the Direct method to close a connection and the C2D message for class C devices, e.g.:

  • we want to send a C2D message to a device using gateway A (last used)
  • the gateway A becomes the losing one (e.g. because a newer message arrived from another gateway) and we close the connection
  • we send the C2D message that will leave the connection open

Acceptance criteria

  • Ensure connections are closed after sending the C2D message
  • Integration test covering this
@spygi spygi added the bug Something isn't working label Mar 3, 2022
@spygi spygi added this to the vNext milestone Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant