-
Notifications
You must be signed in to change notification settings - Fork 426
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.
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
Processor time continues to be used after a failing connect command #136
Comments
Hi @zerasmus , We are aware of the issues you mentioned. Fixes are already merged in our internal dev branch and is pending to be released. Please stay tuned for future releases. Thanks, |
FYI, I believe I've found the issue and a work-around: aws-iot-device-sdk-python/AWSIoTPythonSDK/core/protocol/mqtt_core.py Lines 189 to 200 in 47363e9
The workers are started and then the internal connect raises the exception without stoping the workers.
|
Addressed in v1.4.0. |
I'm trying to write a small script that isn't guaranteed to have internet access on startup and can sometimes lose internet unexpectedly.
When there is no internet, the socket will fail to connect (as expected) due to name resolution not being available. A socket error is raised.
If connect is called again, the error will be raised again, but the processor utilization will increase.
This will continue to occur until the operating system denies you the ability to create threads.
e.x.
Things I've tried:
Connect will have to be called again, since socket lifetimes are limited to 24 hours.
Related: #39 #124
The text was updated successfully, but these errors were encountered: