-
Notifications
You must be signed in to change notification settings - Fork 211
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
RuntimeError (AWS_ERROR_PRIORITY_QUEUE_EMPTY) occurs after 245 connection calls to greengrasscoreipc.connect() #521
Comments
Hi @shomerj, It is hard to say what cause the issue by the error message here. Would you like to provide more logs? Please make sure to remove anything credential information in the log.
|
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. |
The Greengrass IPC client bindings intentionally contain a reference cycle. You must call |
This issue is now closed. Comments on closed issues are hard for our team to see. |
I'll see if there are some places in the documentation where it would make sense to add this information. |
Closing as of #572 |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
Python 3.9, arm32v7, Ubuntu buster
Not sure if this is a bug or explicitly built into the code.
Our system has been receiving RuntimeError after 245 calls when connecting to
awsiot.greengrasscoreipc.connect()
. The specific error message isRuntimeError: 30 (AWS_ERROR_PRIORITY_QUEUE_EMPTY): Attempt to pop an item from an empty queue.
Expected Behavior
Expected connection call to continue to working
Current Behavior
After the 245th established connection
RuntimeError (AWS_ERROR_PRIORITY_QUEUE_EMPTY)
is raised.Reproduction Steps
This code snippet has reproduced the error:
This was also tested with
sleep
added after each call.Possible Solution
No response
Additional Information/Context
No response
SDK version used
1.12.6
Environment details (OS name and version, etc.)
Debian GNU/Linux, Debian 10 (buster)
The text was updated successfully, but these errors were encountered: