Connection does not resume
smnodame opened this issue · 2 comments
Describe the bug
We have used AWS IOT in our product and we have been using it in production already. We found on the customer side that when the network is down and if it back to online, sometimes the connection doesn't resume
we got this log from customer device on 14 Mar but you can see that the latest message is Connection interrupted since last month
2023-02-15T22:01:58.806Z [WARN] (Thread-7) com.aws.greengrass.mqttclient.AwsIotMqttClient: Connection interrupted. {clientId=SCOS_add3-80640777cc21-1656999050, error=Time limit between request and response has been exceeded.}
2023-02-15T22:01:58.819Z [INFO] (Thread-7) com.aws.greengrass.shadowmanager.sync.strategy.BaseSyncStrategy: sync. Stop syncing. {}
2023-02-15T22:01:58.822Z [INFO] (Thread-7) com.aws.greengrass.shadowmanager.sync.strategy.BaseSyncStrategy: sync. Cancel 1 sync thread(s). {}
2023-02-15T22:01:58.826Z [WARN] (pool-2-thread-33) com.aws.greengrass.shadowmanager.sync.strategy.BaseSyncStrategy: sync. Interrupted while waiting for sync requests. {}
2023-02-15T22:01:58.830Z [INFO] (pool-2-thread-33) com.aws.greengrass.shadowmanager.sync.strategy.BaseSyncStrategy: sync. Finished processing sync requests. {}
but yes if we restart the service or reboot the device, it will solve but we want to have it resume automatically to reduce the user effort
Expected Behavior
Connection should resume to connection and status should show back to online
Current Behavior
Connection doesn't resume when the network down and back to online
Reproduction Steps
we do not know how to replicate yet, it might be the edge case but maybe you could notice from the code
Possible Solution
No response
Additional Information/Context
No response
SDK version used
Environment details (OS name and version, etc.)
Our own OS
What do you mean by "Our own OS"?
Could you also include more logs and a minimal code sample that reproduces this?
Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.