You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
We have deployed our application on Docker in an on-premises environment. The application creates a com.microsoft.azure.sdk.iot.device.DeviceClient using an AMQPS connection and listens for incoming data from IoT Hub using the following callback:
Observed Behavior:
Everything works fine in our local environment. However, when testing in the staging environment, we encounter an issue:
Scenario:
If the internet connection is interrupted for an extended period (10-15 minutes), and then the internet connection is restored, the DeviceClient does not receive any messages from IoT Hub until we restart the application.
Expected Behavior:
Even if the internet is down for a long time, once the connection is restored, the DeviceClient should automatically resume receiving messages from IoT Hub without requiring a restart of the application.
Steps to Reproduce:
Deploy the application with DeviceClient using the AMQPS protocol on a Docker container in an on-premises environment.
Interrupt the internet connection for 10-15 minutes.
Restore the internet connection.
Observe that the application no longer receives data from IoT Hub until the application is restarted.
Environment:
Docker-based on-premises environment
com.microsoft.azure.sdk.iot.device.DeviceClient version 2.5.0
AMQPS protocol
Questions:
Is this a known issue with the version of the iot-device-client library we are using?
Are there any recommended configurations or changes that would allow the DeviceClient to automatically reconnect and resume receiving messages after long internet outages?
The text was updated successfully, but these errors were encountered:
The device client library will reconnect for roughly ~4 minutes before giving up by default. This value is configurable, but we generally recommend you also add retry logic within your application layer. We have some sample code that demonstrates how to do that.
Description:
We have deployed our application on Docker in an on-premises environment. The application creates a com.microsoft.azure.sdk.iot.device.DeviceClient using an AMQPS connection and listens for incoming data from IoT Hub using the following callback:
deviceClient.setMessageCallback((message, callbackContext) -> {
com.microsoft.azure.sdk.iot iot-device-client 2.5.0// Handle incoming message
});
Observed Behavior:
Everything works fine in our local environment. However, when testing in the staging environment, we encounter an issue:
Scenario:
If the internet connection is interrupted for an extended period (10-15 minutes), and then the internet connection is restored, the DeviceClient does not receive any messages from IoT Hub until we restart the application.
Expected Behavior:
Even if the internet is down for a long time, once the connection is restored, the DeviceClient should automatically resume receiving messages from IoT Hub without requiring a restart of the application.
Steps to Reproduce:
Deploy the application with DeviceClient using the AMQPS protocol on a Docker container in an on-premises environment.
Interrupt the internet connection for 10-15 minutes.
Restore the internet connection.
Observe that the application no longer receives data from IoT Hub until the application is restarted.
Environment:
Docker-based on-premises environment
com.microsoft.azure.sdk.iot.device.DeviceClient version 2.5.0
AMQPS protocol
Questions:
Is this a known issue with the version of the iot-device-client library we are using?
Are there any recommended configurations or changes that would allow the DeviceClient to automatically reconnect and resume receiving messages after long internet outages?
The text was updated successfully, but these errors were encountered: