Is Azure IoT Hub's DeviceClient thread safe or not?
Is Azure IoT Hub's DeviceClient thread safe or not?
I have a client whose device app gets hung up occasionally, and they haven't been able to figure out why. The device app is a long-running Windows service using the .NET Azure SDK. I've reviewed the code base and have noticed that they have two separate threads each running a loop, with one sending D2C messages, and the other receiving C2D messages, both using the same instance of DeviceClient. Sounds like a potential race condition to me. That makes me wonder if the .NET DeviceClient class is thread safe. Anyone else run into this?
This old (2016) post mentions DeviceClient not being thread-safe, but the current DeviceClient documentation doesn't mention anything about thread safety.
FWIW, they have just over 4000 devices sending around 25MM messages in total per week, and are using MQTT.
Thanks!
deviceClient.SendAsync()
deviceClient.ReceiveAsync()
autoResetEvent
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Hi Vince, I can't reproduce your issue by setting up a timer to call
deviceClient.SendAsync()and whiledeviceClient.ReceiveAsync()is running in another thread, the period of the timer is 1ms. So have you tried the suggestion usingautoResetEventto see if it helps? If you can share the code sample to reproduce this issue I can do a further investigation.– Rita Han - MSFT
Aug 27 at 6:21