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.

Sign up for GitHub

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

Jump to bottom

Hitting the device side client with a bunch of telemetries immediately will create extra (unused) amqp links #957

Closed
anthonyvercolano opened this issue Apr 23, 2021 · 0 comments · Fixed by #966
Closed

Hitting the device side client with a bunch of telemetries immediately will create extra (unused) amqp links #957

anthonyvercolano opened this issue Apr 23, 2021 · 0 comments · Fixed by #966
Assignees
@vishnureddy17
Labels
bug IoTSDK tracks all IoT SDK issues across the board MS-Internal Github issues that are generated internally within MS

Comments

@anthonyvercolano
Copy link
Contributor

Like the title says. Using the amqp transport. Do a bunch of telemetries that don't wait on the callback, one after the other, right after creating the device client. You will get multiple send links. Only one will get used. Leaving the service to fret over the unused ones.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vishnureddy17 vishnureddy17

Labels
bug IoTSDK tracks all IoT SDK issues across the board MS-Internal Github issues that are generated internally within MS
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(azure-iot-device-amqp): 🐛 multiple AMQP links were being created for telemetry
2 participants
@anthonyvercolano @vishnureddy17