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
We're dealing with an issue where celery/kombu/py-amqp stack seems to be losing messages somewhere. Based on the fact the celery task ID is never received by any worker, and the queue being used becomes empty at some point, we're digging into the publishing side.
I've spent the day tracing through the calls to publish a message and noticed py-amqp defines the reject code but doesn't seem to define a handler for a reject response in its _METHODSmap.
Is my understanding correct here? A reject response essentially gets ignored as far as I can tell because AbstractChannel.wait will eat any exception thrown from AbstractChannel.dispatch_method.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We're dealing with an issue where celery/kombu/py-amqp stack seems to be losing messages somewhere. Based on the fact the celery task ID is never received by any worker, and the queue being used becomes empty at some point, we're digging into the publishing side.
I've spent the day tracing through the calls to publish a message and noticed py-amqp defines the reject code but doesn't seem to define a handler for a reject response in its
_METHODS
map.Is my understanding correct here? A reject response essentially gets ignored as far as I can tell because
AbstractChannel.wait
will eat any exception thrown fromAbstractChannel.dispatch_method
.Beta Was this translation helpful? Give feedback.
All reactions