-
Notifications
You must be signed in to change notification settings - Fork 194
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
Built-in TypeError exception from Connection on_inbound_method() #197
Comments
Sorry I cannot provide a simplified test case to point the issue. I think it is somehow related to caching the connections with multiple process / threads involved, I.e. some kind of misuse of the API. I am happy for now that my workaround seems to work with the OpenStack env. |
Hi! I got the similar error.
Python 3.5.5 |
I facing the same issue with openstack/oslo.messaging on queens/OSP13. I can observe some client deconnection/reconnection just before this error will throw. In my case, these errors seems related to vm creations and to heat too... I can't reproduce it merely outside of the openstack scope. I'll try to provide some minimalist POC to test it easily. For further reading about this topic you can take a look to:
|
@4383 Thanks for the detailed report & fix!! can we chat in IRC about the usage of celery in OpenStack? |
@auvipy my pleasure. |
@Perepyolka seems that my issue was fixed by #289 |
There are several reports from the other projects getting this exception when using Connection class:
See for example:
https://bugs.launchpad.net/oslo.messaging/+bug/1504725
celery/kombu#857
celery/kombu#463
Does this mean that Connection class is misused or should there be similar check in on_inbound_method() as there is in channel() for self.channels being None, for example:
I have seen this problem e.g. in OpenStack Pike when creating heat stacks and stack creation can fail for that TypeError exception. If I add above check it seems that client can re-connect and stack creation does not fail (when RecoverableConnectionError is thrown instead of TypeError).
The text was updated successfully, but these errors were encountered: