Closed ghost closed 7 years ago
Hi @davidbuechi , thanks for reporting the issue.
We will verify the scenario and reply back briefly.
We were able to repro the issue. An update will be sent soon once we root-cause and correct the problem.
As a note, the issue does not repro at this point using SAS authentication, only x509.
Linking to #184
This issue was root-caused and the fix is being tested. We will make it available on the master branch soon.
Hi @davidbuechi , a fix was just checked in for this issue, please verify if you have a chance and let us know.
Thanks, Azure IoT Team.
I've done some tests with bac8131fd232c7bbc7ac4243d6b2860c9668d6c6. It does not crash anymore. However, it also does not always re-establish the connection, see issue #274
Hi @davidbuechi , since this is a new issue, it would have been better to open a new separate one. That helps make it more visible to all customers, and allows us to close on the previous one.
We will verify the issue above and reply back soon.
@davidbuechi , in your application did you explicitly set the IoTHubClient to use IMMEDIATE retry policy? Similar to the call bellow?
IoTHubClient_SetRetryPolicy(iothubClientHandle, IOTHUB_CLIENT_RETRY_IMMEDIATE, 600);
Thanks @davidbuechi , we will follow up on the other issue.
Closing this one. Thanks.
OS and version used: Ubuntu 16.04.3 LTS and Yocto Linux (Krogoth branch)
SDK version used: 2017-10-09 / 1.1.25
Protocol: verified with AMQP and AMQP over Websockets
Description of the issue:
After a successfull connection the network is disconnected. A few minutes later the application crashes.
Code sample exhibiting the issue:
Take the
iothub_client/samples/iothub_client_sample_x509/iothub_client_sample_x509.c
and:#define MESSAGE_COUNT 5
to#define MESSAGE_COUNT 1000
ThreadAPI_Sleep(1;
in the while loop toThreadAPI_Sleep(1000)
Console log of the issue:
start the application:
disconnect the network: